Have your user data stored in an application which supports only custom API Authentication ? Looking for a Single Sign-On Solution? Don’t want the hassle of developing, maintaining and integrating with your application?
This guide will help you implement Single Sign-On and for your user-store/application via their existing API Authentication and miniOrange broker service.
Connect your existing CMS like WordPress, Joomla, Drupal, Magento etc or any application that support custom API authentication with miniOrange and SSO into any other application without having to move your users.
You can configure your Magento ( version 1.5-1.9 ) site as an authentication source and Single Sign-On into any other application.
Here are the steps on how to configure Magento as an authentication source:
You can configure your Magento ( version 2.0 and up ) site as an authentication source and Single Sign-On into any other application.
Here we are the steps on how to configure Magento as an authentication source:
|<Your miniOrange Email>|
|Identity Link URL||https://www.miniorange.com|
|Your Password||<Your Admin Password>|
With us, You can configure application according to the the protocol it supports like SAML, OAuth, JWT, Ws-fed etc.
|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: Choice 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 also have a choice to set multiple IDPS for Single Application. And there are two ways to represent them :
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.