Need Help? We are right here!
Thanks for your Enquiry. Our team will soon reach out to you.
If you don't hear from us within 24 hours, please feel free to send a follow-up email to info@xecurify.com
Search Results:
×Microsoft Entra ID SSO login [SAML SSO] can be achieved by using the miniOrange Brokering Solution. This Brokering Microsoft Entra ID SSO solution allows users to login into multiple applications using an existing username and password of Microsoft Entra ID IDP.
Here Microsoft Entra ID will act as an Identity Provider (IDP) and your applications will act as a Service Provider (SP). miniOrange acts as a broker to communicate with IDP and SP and provide secure login access to users. Microsoft Entra ID handles the responsibility of authenticating users within the application, making it easier for admins to integrate SSO into their applications. Overall this eliminates the need to manage different identities as all information is stored in a unified location - Microsoft Entra ID.
Once Microsoft Entra ID SSO is configured, you will be able to get most of advanced SSO features:
miniOrange offers free help through a consultation call with our System Engineers to configure SSO for different apps using Microsoft Entra ID as IDP in your environment with 30-day free trial.
For this, you need to just send us an email at idpsupport@xecurify.com to book a slot and we'll help you in no time.
https://<custom_domain>.xecurify.com/moas/login
Mentioned below are steps to configure Microsoft Entra ID as IDP via SAML and OAuth configuration. Follow the steps accordingly based on your requirement (SAML or OAuth).
Follow the steps to configure Microsoft Entra ID as IdP by OAuth configuration.
IdP Name | Custom Provider |
IdP Display Name | Choose appropriate Name |
OAuth Authorize Endpoint | https://{your-base-url}/as/authorization.oauth2 | OAuth Access Token Endpoint | https://{your-base-url}/as/token.oauth2 | OAuth Get User Info Endpoint (optional) | https://{your-base-url}/idp/userinfo.oauth2 |
Client ID | From step 1 |
Client secret | From step 1 |
Scope | auto |
If you have already configured your application in miniOrange you can skip the following steps.
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 |
Description | 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.
https://{mycompany.domainname.com}/moas/idp/openidsso
https://{mycompany.domainname.com}/broker/login/oauth{customerid}
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
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.
You receive these error message when you try to SSO in to an application that has been set up to use Microsoft Entra ID as External IdP using SAML-based Single Sign-On (SSO).
The user hasn't been granted access to the application in Microsoft Entra ID. The user must belong to a group that is assigned to the application, or be assigned directly.
To assign one or more users to an application directly, see Quickstart: Assign users to an app.
The application object is corrupted and Microsoft Entra ID doesn't recognize the certificate configured for the application.
To delete and create a new certificate, follow the steps below:
The AssertionConsumerServiceURL value in the SAML request doesn't match the Reply URL value or pattern configured in Microsoft Entra ID. The AssertionConsumerServiceURL value in the SAML request is the URL you see in the error.
To fix the issue, follow these steps:
The Issuer attribute sent from miniOrange to Microsoft Entra ID in the SAML request doesn’t match the Identifier value configured for the miniOrange in Microsoft Entra ID.
Ensure that the Issuer attribute in the SAML request matches the Identifier value configured in Microsoft Entra ID.
Verify that the value in the Identifier textbox matches the value for the identifier value displayed in the error.
The Issuer attribute sent from the application to Microsoft Entra ID in the SAML request doesn’t match the Identifier value that's configured for the application in Microsoft Entra ID.
Ensure that the Issuer attribute in the SAML request matches the Identifier value configured in Microsoft Entra ID.
On the SAML-based SSO configuration page, in the Basic SAML configuration section, verify that the value in the Identifier textbox matches the value for the identifier value displayed in the error. If there's a trailing slash at the end of the url, it should be also included.
Microsoft Entra ID doesn't support the SAML request sent by the miniOrange for single sign-on. Some common issues are:
Capture the SAML request in SAML Tracer.
Contact us and share the following info:
To learn how to customise the SAML attribute claims sent to your application, see Claims mapping in Microsoft Entra ID. And also, see below the attribute mapping in miniOrange.
In Azure portal, you can access the logs to verify successful logins. This will help establish a baseline for successful authentication. Whenever login access is denied, closely review the login attempts in the logs.
Addressing Login Issues Without Azure:
You can use the SAML-tracer extension for Chrome to diagnose and resolve SAML-related problems in Operations Hub. Follow these steps:
Retrieving Azure Login Screen:
In case you encounter a situation where the Azure login screen does not appear, then do the following to address this issue:
Our Other Identity & Access Management Products