miniOrange SSO solution allows you to login to any of your applications/websites using SURFconext as IdP (Identity Provider). In this guide we will go through step-by-step instructions on how to configure SSO between an application and SURFconext by configuring SURFconext as an Identity Provider and your application as a Service Provider.
miniOrange SSO solution also acts as an identity broker for cross protocol authentication, which means Service Provider following a particular SSO protocol can connect to an Identity Provider following some different SSO protocol like SAML,OAuth etc. Once configured successfully you will be ready to securely access your website/application using SURFconext IDP.
|IdP Entity ID||Identity Provider Issuer from SURFconext|
|SAML SSO Login URL||Identity Provider Single Sign-On URL from SURFconext|
|X.509 Certificate||X.509 Certificate from SURFconext|
|Single Logout URL [Optional]||Single Logout URL from SURFconext|
|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|
|From existing entity||No, create blank registration form|
|Single sign on URL||ACS URL|
|Audience URI (SP Entity ID)||Entity ID or Issuer|
You have successfully configured SURFconext as SAML IdP (Identity Provider) for achieving Single Sign-On.
|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 you can achieve this by using the following steps:- Our domain mapping feature
Lets say, there are two organisations under ADFS. One want to authenticate the users under the domain demo.com and other one with the domain example.com. For reference, We have taken the 2 organisations as two different IDPs and WordPress as SP. Follow the guides to set up ADFS 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.
Need Help? We are right here!