Choose a name for your identity provider. This is the user-facing name, so choose a name your users will recognize. This value can be changed later.
Select how the user will be redirected to the identity provider. You may configure more redirect modes after completing the setup.
Copy and save the Callback URL for later. You will need this when configuring Okta.
If you are using SCIM with your provider, make sure to check out the documentation for configuring this before proceeding. It might be that you need to configure this first or at the same time as setting up OIDC. |
Login to Okta as an admin user.
Go to Applications → Applications in the menu and choose Create App Integration.
Choose OIDC as Sign-in method and Web application as Application type.
Choose an appropriate name for your App integration.
Remove any default values from the Sign-out- and Sign-in redirect URIs field and paste the Callback URL from the KSSO setup wizard in the Sign-in redirect URIs field.
Under Assignment, choose an assignment method for assigning users and groups to the App integration. You can also choose the skip option to do this at a later time.
Save your changes.
On the next page, copy and keep the Client ID and Client secret for later use. You will need these for a later step in the KSSO setup guide.
Go back to the Kantega SSO setup wizard.
I the Metadata step replace the {idp_url} placeholder with your Okta host to complete the Discovery URL.
These are the scopes we were able to fetch from the metadata. You can add scope values from a list, start typing to add your own or unselect them. A minimum of one scope value is required.
Paste the Client ID and Client Secret you kept from the Okta App integration settings earlier .
Check that everything looks good and submit your setup 
Test that logging in with Okta works as expected. This will help identify if there are any issues with the configuration. Follow the steps to perform the login test.
