Need Help? We are right here!
Amazon Web Services (AWS IAM) Single Sign-On solution by miniOrange allows all system users to access all authorized system resources with a single username and password. AWS IAM SSO solution provides a single way to manage access to the AWS console, AWS command line interface, and AWS IAM Identity Center enabled applications centrally.
You can provision and deprovision roles, assignments, and trust configurations automatically across multiple AWS accounts. After enabling the AWS IAM SSO solution, the end user will be able to access their AWS accounts along with their assigned roles and also will be signed into AWS IAM Identity center enabled applications.
Benefit of using AWS IAM SSO Integration
AWS IAM Single Sign-On (SSO) makes it easier for AWS administrators to set up roles & assign access across multiple AWS accounts. Customers can use AWS IAM SSO to connect an identity source to AWS once and then manage access to AWS centrally. Individual accounts do not require any additional settings. AWS IAM SSO works in conjunction with AWS.
miniOrange offers free help through a consultation call with our System Engineers to Install or Setup AWS IAM SSO solution in your environment with 30-day free trial.
For this, you need to just send us an email at email@example.com to book a slot and we'll help you in no time.
In this flow, the user tries to login to the Serivce Provider (AWS account) directly. The request is redirected to the Identity Provider for authentication. On sucessfull authentication from the Identity provider, the user is given access to the application (AWS account).
In this flow, the user logs in to the Identity Provider using his credentials. Now the user can access any of the configured Service Providers (AWS account, etc.) through the Identity Provider Dashboard without having to enter the credentials agian.
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Shibboleth, Ping, Okta, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more.
Test SSO login to your AWS IAM account with miniOrange IdP:
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.
1. Create User in miniOrange
2. Bulk Upload Users in miniOrange via Uploading CSV File.
Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.
|Activate LDAP||All user authentications will be done with LDAP credentials if you Activate it|
|Sync users in miniOrange||Users will be created in miniOrange after authentication with LDAP|
|Fallback Authentication||If LDAP credentials fail then user will be authenticated through miniOrange|
|Allow users to change password||This allows your users to change their password. It updates the new credentials in your LDAP server|
|Enable administrator login||On enabling this, your miniOrange Administrator login authenticates using your LDAP server|
|Show IdP to users||If you enable this option, this IdP will be visible to users|
|Send Configured Attributes||If you enable this option, then only the attributes configured below will be sent in attributes at the time of login|
Refer our guide to setup LDAPS on windows server.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.
A. Restricting access to AWS IAM with IP Blocking
You can use adaptive authentication with AWS IAM Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.You can configure Adaptive Authentication with IP Blocking in following way:
|Allow||Allow user to authenticate and use services if Adaptive authentication condition is true.|
|Challenge||Challenge users with one of the three methods mentioned below for verifying user authenticity.|
|Deny||Deny user authentications and access to services if Adaptive authentication condition is true.|
|User second Factor||The User needs to authenticate using the second factor he has opted or assigned for such as
|KBA (Knowledge-based authentication)||The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further.|
|OTP over Alternate Email||User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further.|
B. Adaptive Authentication with Limiting number of devices.
Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.You can configure Adaptive Authentication with Device Restriction in following way
C. Add Adaptive Authentication policy to AWS IAM.
D.Notification and Alert Message.
This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :
|Challenge Completed and Device Registered||Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.|
|Challenge Completed but Device Not Registered||Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.|
|Challenge Failed||Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.|
1. BAD REQUEST (Status Code: 400):
2. IDP Initiated
3. Troubleshoot other common errors HERE.
Our Other Identity & Access Management Products