Integration detailFree trial with Okta + Add Integration
SAP SuccessFactors Human Experience Management (HXM) Suite helps you to completely reinvent the entire employee experience. You can shift from traditional HR transactions to engaging end-to-end experiences that use intelligent technology, so each interaction is simpler and more meaningful. By linking employee feedback to operational data, you'll understand what's happening and why, so you can continuously deliver exceptional experiences that help to keep your business growing and your employees happy.
The built-in provisioning functionality of Okta, in combination with the lifecycle management event triggers provided by SuccessFactors HXM, seamlessly drives IT process changes into downstream applications. Together, they ensure that your employees have the right access to the applications, systems, and processes when they need it.
HR and IT departments face an ongoing communication challenge: HR Information Systems (HRIS) like SuccessFactors need to share data from employee profiles so that IT can create new user accounts, provision them for access to applications, and deactivate employees when they leave the company. As more and more enterprise activity moves to the cloud, and as companies grow in size and complexity, HR and IT need a better, more efficient, and less risky system for managing the employee lifecycle.
- Process inefficiency: Sending data via email, attachments, or file extracts is time-consuming and error prone
- Security weaknesses: Completely deprovisioning users takes two days, on average, putting enterprise data at risk
- Unproductive employees: Inefficiency leaves employees waiting for apps and updated permissions
Okta’s pre-built integration with SuccessFactors brings HR and IT systems together, letting user data and profile updates in SuccessFactors inform the user lifecycle across IT systems. Connecting HR and IT systems, including apps and Active Directory, takes the time, friction, and risk out of managing employee data and permissions.
Add this integration to enable authentication and provisioning capabilities.
- Event Hooks
- Inbound Federation
- Inline Hooks
- Outbound Federation
- SAML Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP) that does not require credentials to be passed to the service provider.
- Workflow Templates
- Workflows Connectors
- SWA Secure Web Authentication is a Single Sign On (SSO) system developed by Okta to provide SSO for apps that don't support proprietary federated sign-on methods, SAML or OIDC.
- OIDC OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service provider (SP) and does not require credentials to be passed from the Identity Provider to the application.
- Create Creates or links a user in the application when assigning the app to a user in Okta.
- Update Okta updates a user's attributes in the app when the app is assigned. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.
- Deactivate Deactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Accounts can be reactivated if the app is reassigned to a user in Okta.
- Attribute Sourcing The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.
- Sync Password Push either the users Okta password or a randomly generated password to the app. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password.
- Group Push Push existing Okta groups and their memberships to the application. Groups can then be managed in Okta and changes are reflected in the application.
- Group Linking Link Okta groups to existing groups in the application. Simplifies onboarding an app for Okta provisioning where the app already has groups configured.
- Schema Discovery Import the user attribute schema from the application and reflect it in the Okta app user profile. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema.
- Attribute Writeback When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.
Here is a section all about documentation, integration, and implementation.