miniOrange allows you to authenticate your users via API authentication provider into multiple applications.
This way, you can achieve Single Sign-On (SSO) into your applications where the users will need to authenticate themselves via your API Server only once and they can access all the configured applications.
In API key authentication, a key-value pair is sent to the API Server either in Request headers or in request body.
For application specific guides of Wordpress, Moodle, Magento, refer our IDP Setup Guides.
User Authentication URL | Your API Authentication provider URL. Eg: https://example.com/endpoint/ |
API Key | The API key value provided by your API Authentication Provider |
In this method, The API key is sent as "Authorization_key" via request header. You can refer to the example below.
Authentication Parameters | { "username":"##username##", "password":"##password##" } |
Status | Name of field in the server response that contains the status code |
Staus Message | Name of the field that gives the description of the status in the response |
In this method, The API key is sent as "api_key" parameter in the POST body as JSON.
To configure your provider to send API key as a field in request body, you can refer below.
Authentication Parameters | { "api_key":"value", "username":"##username##", "password":"##password##" } |
Put the API key value that you copied in step 1 in place of 'value'. |
Status | Name of field in the server response that contains the status code |
Staus Message | Name of the field that gives the description of the status in the response |
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 |
Response Signed | Unchecked |
Assertion Signed | Checked |
Encrypted Assertion | Unchecked |
Group policy | Default |
Login Method | Password |
Client Name | Add appropriate Name |
Redirect URL | Get the Redirect-URL from your OAuth Client |
Descrption | Add if required |
Group Name | Default |
Policy Name | As per your Choice |
Login Method | Password |
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.
https://login.xecurify.com/moas/jwt/mobile
You also have a choice to set multiple IDPS for Single Application. And there are three 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.