Experian - ID Proofing
Okta and Experian provide complementary solutions in the end-user registration workflow, in that Okta provides user registration and authentication and Experian can provide Identity Proofing services that give an application a level of confidence about the user who is trying to register. The use-case for identity proofing usually falls into one of three main scenarios: Fraud prevention (I am a consumer trying to open a bank account or obtain an insurance policy, for example) Privileged access (I will have access to protected information online, so the application needs more confidence that I am who I say I am) Proof of membership in a particular demographic (this web site offers a 15% discount for teachers, so I need to provide my staff ID during the checkout workflow)
- Identity spoofing is a common way for hackers to access a company’s sensitive data
- Industry studies show that about 80% of data breaches are the result of stolen or weak credentials
- Enterprises that handle sensitive information – such as healthcare, consumer finance, insurance organizations, and government agencies – need deeper levels of identity security
User self-registration with ID proofing service
Keep sensitive information out of the wrong hands
Leverage Experian’s unparalleled experience in gathering—and safeguarding—consumer information, together with Okta’s industry-leading identity management and provisioning technology, to add an extra layer of identity assurance that keeps sensitive information from falling into the wrong hands.
- 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.
- 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.
- 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.
- 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.
- 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 Mastering 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.
- 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.