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:
×miniOrange Identity Broker service solution enables cross protocol authentication. You can configure AWS Cognito as an IDP for Single Sign-On (SSO) into your applications/websites. Here, AWS Cognito will act as an Identity Provider (IDP) and miniOrange will act as a broker.
We offer a pre-built solution for integrating with AWS Cognito, making it easier and quick to implement. Our team can also help you set up AWS Cognito as OIDC IDP to login into your applications.
miniOrange offers free help through a consultation call with our System Engineers to configure SSO for different apps using AWS Cognito 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.
Please make sure your organisation branding is already set under Customization >> Login and Registration Branding in the left menu of the dashboard.
Note: If you would like to customize the AWS login page kindly choose AWS as the Userstore. For the default AWS login page, you can go with AWS as IdP configurations.
1.1 Configuring miniOrange as Service Provider (SP) in AWS Cognito
1.1 Configuring miniOrange as Userstore in AWS Cognito
A] Steps to Configure User Pool
B] Steps to Configure Identity Pool
IdP Name | Custom Provider |
IdP Display Name | Choose appropriate Name |
OAuth Authorize Endpoint | https://{cognito-app-domain}/oauth2/authorize | OAuth Access Token Endpoint | https://{cognito-app-domain}/oauth2/token | OAuth Get User Info Endpoint (optional) | https://{cognito-app-domain}/oauth2/userInfo |
Client ID | From above step |
Client secret | From above step |
Scope | openid email phone profile |
AWS Cognito Identifier | Provider Name |
AWS Cognito Region | Get Cognito region from user pool(eg.us-east-2) |
Identity Pool ID | From step 1.2 |
User Pool ID | From step 1.1 |
Client ID | From step 1.1 |
You can follow this guide, if you want to configure SAML/WS-FED, OAuth/OIDC, JWT, Radius etc
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 AWS Cognito as External IdP using OAuth based Single Sign-On (SSO).
This error occurs when the redirect URI specified in the authentication request doesn’t match the one registered in Cognito.
This error typically arises when the Client ID or Client Secret in the OAuth request is incorrect.
If your OAuth request lacks necessary scopes (e.g., 'openid', 'email', or 'profile'), AWS Cognito will throw this error.
This error often occurs if there is an issue with the authorization code or refresh token used to get tokens.
This means the OAuth client (application) is not allowed to use the specific flow (e.g., authorization code, implicit, or client credentials).
This occurs when the user denies consent or the client app doesn’t have permission to request specific scopes.
Our Other Identity & Access Management Products