Okta Single Sign On (SSO) for Your Application miniOrange provides a ready to use solution for Your application.Single Sign on (SSO) for your application with Okta as Identity Provider and miniOrange can act as a service provider or an identity Broker.
Using our identity broker service you can easily SSO into any app. You can configure Okta IDP which supports SAML to single sign-on into apps that support SAML or any other protocols like OAuth, OpenID Connect, JWT, etc. Our Identity Broker service enables cross protocol authentication. Follow the easy steps given in this guide to login using Okta.
Note: Switch to Classic UI from Okta Developer Console, by selecting the Admin from the upper right corner then Developer Console > Classic UI
|Single sign on URL||ACS URL|
|Audience URI (SP Entity ID)||Entity ID or Issuer|
|Encryption Certificate||This is optional|
|Enable Single Logout||Enable the check box to Allow application to initiate Single Logout|
|Single Logout URL||Single Logout URL as mentioned in the Metadata Section|
|SP Issuer||Entity ID or Issuer as mentioned in the Metadata Section|
|Signature Certificate||X.509 Certificate can be downloaded from the Metadata Section|
|IdP Entity ID||Identity Provider Issuer from Okta|
|SAML SSO Login URL||Identity Provider Single Sign-On URL from Okta|
|X.509 Certificate||X.509 Certificate from Okta|
|Single Logout URL [Optional]||Single Logout URL from Okta|
|Domain Mapping||Can be used to redirect specific domain user to specific IDP|
|Show IdP to Users||Enable this if you want to show this IDP to all users during Login|
|Send Configured Attributes||Enabling this would allow you to add attributes to be sent from IDP|
|Service Provider Name||Choose appropriate name according to your choice|
|SP Entity ID or Issuer||Your Application Entity ID|
|ACS URL X.509 Certificate (optional)||Your Application Assertion Consumer Service URL|
|NameID Format||Select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress|
|Client Name||Add appropriate Name|
|Redirect URL||Get the Redirect-URL from your OAuth Client|
|Descrption||Add if required|
|Policy Name||As per your Choice|
Note: Choose the Authorization Endpoint according to the identity source you configure.
In case you are setting up SSO with Mobile Applications where you can't create an endpoint for Redirect or Callback URL, use below URL.
You have a choice to set multiple IDPS for Single Application, i.e integrate multiple IDP and users can select IDP accordingly from which they want to authenticate themselves. There are three different ways to authenticate users using IDP.
Note : At once you can select either of them.
Few usecases where customers configure multiple IDPs -
|For Cloud IDP -||https://login.xecurify.com/moas/discovery?customerId=<customer_id>|
|For On-Premise IDP -||https://yourdomain.com/discovery?customerId=<customer_id>|
You can see the screenshot below of the IDP Selection Page with a list of IDPs .
Note: To view the IDP in drop-down list, go to Identity Providers tab > against your configured IDP > Select >Edit , here Enable the Show IdP to Users option.
If you have multiple IDPs and you want a certain set of users to authenticate from one IdP whereas another set of users to authenticate from another IdP, based on their email domains then you can achieve this by using the following steps:- Our domain mapping feature
For your reference , Azure AD and Okta is being used as two different IDPs and WordPress is being used as SP. Follow the guides to set up Okta and WordPress at your end.
If you have multiple IDPs (identity provider) and you want a certain application user to authenticate with one IDP and other application users with another IDP then you can achieve this by our Identity Source Feature.