Create and configure a duplicate app instance
Okta provisioning can be enabled on an SSOAn acronym for single sign-on. In a SSO system, a user logs in once to the system and can access multiple systems without being prompted to sign in for each one. Okta is a cloud-based SSO platform that allows users to enter one name and password to access multiple applications. Users can access all of their web applications, both behind the firewall and in the cloud, with a single sign in. Okta provides a seamless experience across PCs, laptops, tablets, and smartphones.-enabled appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. without breaking the SSO functionality. However, if you would rather not make any changes to your SSO-enabled app, you can create another instance of the app with Okta provisioning enabled. The SSO-enabled app and the provisioning-enabled app are "linked" through the use of common user folders. This allows provisioning to the SSO-enabled app.
- On the Okta AdminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page. Console, click Applications.
- Click Add Application.
- Enter the name of the application in the Search for an application field and click Add next to the application you want to add. The application should have Okta verification, SAMLAn acronym for Security Assertion Markup Language, SAML is an XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP). The SAML standard addresses issues unique to the single sign-on (SSO) solution, and defines three roles: the end user, the IdP, and the SP. Here's how SAML works through Okta: SP-initiated flow: the end user requests (principally through a browser) a service from the SP. The SP requests and obtains an identity assertion from the IdP (in this case, Okta). On the basis of this assertion, the SP can decide whether or not to authorize or authenticate the service for the end user. IdP-initiated flow: with Okta as the IdP, an end user goes to the Okta browser and clicks on an app, sending a SAMLResponse to the configured SP. A session is established with the SP, and the end user is authenticated. authentication, and allow provisioning.
- In the Application label field, enter a name for the duplicate app.
- Complete the remaining fields and click Next.
- Complete the SIGN ON METHODS, ADVANCED SIGN-ON SETTINGS, and CREDENTIALS DETAILS sections and click Done.
Make sure the option you select in the Application username format list is the same format used in the application you are duplicating.
- Click Done.
- Complete the application provisioning settings. See Configure application provisioning.