Search Results :×
Azure AD Single Sign On (SSO) for Your Application solution from miniOrange secures your application behind the SSO login, allowing users to get authenticated using their Azure AD login credentials.
Our Azure AD Single Sign-On (SSO) solution establishes trust between your application and Azure AD allowing user to login into application using their Azure As credentails.
The solution also supports advanced SSO features like Attribute & Group Mapping, Synchronize user’s details with Azure AD.
Using the setup guide below, you can easily configure Single Sign-On (SSO) login between your SAML Application or OAuth Application and Azure AD by considering Azure AD as IdP (Identity Provider) and Your SAML application or OAuth Application as SP (Service Provider), with miniOrange acting as intermediate agent between the two.
Mentioned below are steps to configure Azure AD as IDP via SAML and OAuth configuration. Follow the steps accordingly based on your requirement (SAML or OAuth).
Follow the steps to configure Azure AD as IdP by SAML configuration.
|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|
Follow the steps to configure Azure AD as IdP by OAuth configuration.
|IdP Name||Custom Provider|
|IdP Display Name||Choose appropriate Name|
|OAuth Authorize Endpoint||From step 1||OAuth Access Token Endpoint||From step 1||OAuth Get User Info Endpoint (optional)||-|
|Client ID||From step 1|
|Client secret||From step 1|
|Identifier (Entity ID)||Entity ID or Issuer|
|Reply URL (Assertion Consumer Service URL)||ACS URL|
|Sign on URL (optional required during IDP-initiated SSO)||Show SSO Link from Step 4|
|Logout URL||Single Logout URL|
|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.
Using this Guide, you have successfully configured Azure AD Single Sign-On (Azure AD SSO Login) for Your Application by configuring Azure AD as IdP and your SAML Applications as SP using our Azure AD Single Sign On (SSO) for Your Application solution.
This solution ensures that you are ready to roll out secure access to your applications using Azure AD login credentials within minutes.
Same steps can be followed to configure Single Sign-On (SSO) login between other Protocol supporting Applications (Oauth, OpenID etc.)
If you couldn't find what you were looking for, please drop us an email on firstname.lastname@example.org. We will reach out at the earliest.
Need Help? We are right here!
Thanks for your inquiry.
If you dont hear from us within 24 hours, please feel free to send a follow up email to email@example.com
Necessary cookies help make a website fully usable by enabling the basic functions like site navigation, logging in, filling forms, etc. The cookies used for the functionality do not store any personal identifiable information. However, some parts of the website will not work properly without the cookies.
These cookies only collect aggregated information about the traffic of the website including - visitors, sources, page clicks and views, etc. This allows us to know more about our most and least popular pages along with users' interaction on the actionable elements and hence letting us improve the performance of our website as well as our services.