? SLX - AWS SSO
support@securelynkx.com +91 9310066015



SINGLE SIGN-ON (SSO) FOR AMAZON WEB SERVICES (AWS)


SLX Connect provides a ready to use AWS SSO solution. AWS Single Sign-on (SSO) solution ensures that you are ready to roll out secure access for login to AWS (Amazon Web Services) to your users within minutes.


AWS Single Sign-On (SSO)

AWS SSO is a cloud based Single Sign-On solution which provides secure access to Amazon web services and full access to multiple cloud Applications with one set of login credentials. Specifically, it helps you manage SSO access and user permissions across all your AWS accounts as well as custom applications that support Security Assertion Markup Language (SAML) 2.0. AWS SSO integration by SLX Connect provides a special-case where users can find access to all their assigned AWS accounts, cloud applications, and custom applications in one place.


SLX Connect Identity Management Features

  • Single Sign-On

    SLX Connect Single Sign-On (SSO) Solution provides easy and seamless access to all enterprise resources with one set of credentials. SLX Connect also provides secure authentication by establishing a trust relationship between the Service Provider and Identity Provider. SLX Connect Single Sign-On supports SSO to any type of device or application whether they are in the cloud or on-premise.

  • Multi-factor Authentication

    Secure your Amazon Web Services(AWS) application from password theft using multi-factor authentication methods with 15+ authentication types provided by SLX Connect. Our multi-factor authentication methods prevent unauthorized users from accessing information and resources having passwords alone as an authentication factor. Enabling second-factor authentication for Amazon Web Services(AWS) protects you against password thefts.

  • IP Blocking

    SLX Connect provides IP blocking/IP restriction for Amazon Web Services(AWS) login which adds security to Gmail, Web, and other applications. In this, we provide you option for IP blocking which includes both automatic (based on user behavior) and manual IP blocking which includes blacklisting and whitelisting of IP addresses to provide access restriction, the office only access, intranet access & network restriction. Learn More

  • Adaptive Authentication

    SLX Connect Adaptive Authentication aims to provide a better experience to reduce the authentication burden on users while enforcing strong authentication where it is needed the most. For example, when a user attempts to access an application via an unregistered device then they may be prompted to register it. If the user logs in from a geographical location other than their office, they may be asked to answer security questions.

  • User Provisioning

    SLX Connect User Provisioning provides an easy way of creation, management, and maintenance of end-users especially for large enterprises to reduce the risk for unauthorized access of information. User provisioning includes the creation, updating and deletion of user accounts. User provisioning makes life easier for admins because they do not have to manually arrange access for each user.

  • Amazon Web Services (AWS) supports only IdP (Identity Provider) initiated Single Sign-On (SSO)

      In IdP Initiated Login, SAML request is initiated from SLX Connect IdP.

      • Enduser first authenticates through SLX Connect Idp by login to SLX Connect Self Service Console.
      • On User Dashboard , there is a Amazon Web Services (AWS) icon, when the enduser clicks on the icon he will be redirected to his Amazon Web Services (AWS) Account - there is no need to login again.

    SLX Connect supports both IdP (Identity Provider) and SP (Service Provider) initiated Single Sign On (SSO)

    • IdP Initiated Single Sign On (SSO)

      In IdP Initiated Login, SAML request is initiated from SLX Connect IdP.

      • Enduser first authenticates through SLX Connect Idp by login into SLX Connect Self Service Console.
      • The Enduser will be redirected to their Amazon Web Services(AWS) account by clicking the Amazon Web Services(AWS) icon on the Enduser Dashboard - there is no need to log in again.
    • SP Initiated Single Sign On (SSO)

      In SP Initiated Login, SAML request is initiated by Amazon Web Services(AWS).

      • An Enduser tries to access their Account by going to Amazon Web Services(AWS) domain.
      • Here they can enter the SLX Connect login credentials and login to their Amazon Web Services(AWS) Account.


  • Microsoft AD


    Azure AD


    SLX Connect IDP



    ADFS


    Google


    Shibboleth




    Ping


    Okta



    AWS Cognito


    Keylock



    One Login


    Centrify

    Follow the Step-by-Step Guide given below to enable AWS SSO.

    Step 1: Configure Amazon Web Services(AWS) in SLX Connect

    • Login into SLX Connect Admin Console.
    • Go to Apps >> Manage Apps.
    • Amazon Web Services(AWS) Single Sign-On (SSO) manage apps


    • Click on Add Applicaton button.
    • Amazon Web Services(AWS) Single Sign-On (SSO) add app


    • In Choose Application Type click on Create App button in SAML/WS-FED application type.
    • Amazon Web Services(AWS) Single Sign-On (SSO) choose app type


    • In the next step, search for your application from the list, if your application is not found. Search for "custom" and you can set up your app via Custom SAML App.
    • Amazon Web Services(AWS) Single Sign-On (SSO) manage apps


    • Get the SP Entity ID or Issuer from the metadata (https://signin.aws.amazon.com/static/saml-metadata.xml). You will find the value in the first line against entityID. It is set to urn:amazon:webservices but may vary for non-US regions.
    • Make sure the ACS URL is: https://signin.aws.amazon.com/saml . This might vary for non-US regions in which case you would find it in metadata ( https://signin.aws.amazon.com/static/saml-metadata.xml) as Location attribute of AssertionConsumerService.
    • Click on Show Advanced Settings. Against Relay State select Custom Attribute Value & enter https://console.aws.amazon.com.
    • Enable Override RelayState.


    • You can set another value for relay state depending on where you want to redirect user after SSO.
    • Go to the Add Policy and select DEFAULT from the Group Name dropdown.
    • Now enter the AWS in the Policy Name field.
    • Select PASSWORD from the First Factor Type dropdown.
    • Click on Save button to configure AWS.
    • Amazon Web Services (AWS) SSO add policy


    • Click on Save to configure AWS.
    • Once the App is added, click on the Metadata link, download metadata file and keep with you which you will require later.
    • Amazon Web Services (AWS) SSO click metadata link


    • Keep SAML Login URL , SAML Logout URL and click on the Download Certificate button which you will required for further.

    • Amazon Web Services (AWS) SSO configuration metadata details

      Step 2: Choose Your User Directory

      2.1: Setup AD as User Directory

      1. Login to SLX Connect dashboard from the Admin Console.
      2. From the left side menu, click on User Stores >> Add User Store.


      3. Select User Store type as AD/LDAP.


        1. STORE LDAP CONFIGURATION IN SLX Connect: Choose this option if you want to keep your configuration in SLX Connect. If active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
        2. STORE LDAP CONFIGURATION ON PREMISE: Choose this option if you want to keep your configuration in your premise and only allow access to AD inside premises. You will have to download and install SLX Connect gateway in your premise.


      4. Enter LDAP Display Name and LDAP Identifier name.
      5. Select Directory Type as Active Directory.
      6. Enter the LDAP Server URL or IP Address against LDAP Server URL field.
      7. Click on Test Connection button to verify if you have made a successful connection with your LDAP server.


      8. In Active Directory, go to the properties of user containers/OU's and search for Distinguished Name attribute.
      9. Amazon Web Services(AWS)  Single Sign-On (SS0)configure user bind account domain name


      10. Enter the valid Bind account Password.
      11. Click on Test Bind Account Credentials button to verify your LDAP Bind credentials for LDAP connection.
      12. Amazon Web Services(AWS)  Single Sign-On (SS0)check bind account credentials


      13. Search Base is the location in the directory where the search for a user begins. You will get this from the same place you got your Distinguished name.
      14. Amazon Web Services(AWS)  Single Sign-On (SSO) configure user search base


      15. Select a suitable Search filter from the drop down menu. To use custom Search Filter select "Custom Search Filter" option and customize it accordingly.
      16. Amazon Web Services(AWS) Single Sign-On (SSO)select user search filter


      17. You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Save button to add user store.
      18. Amazon Web Services(AWS) Single Sign-On (SSO) Activate ldap options


        Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.

        Attribute Description
        Activate LDAP All user authentications will be done with LDAP credentials if you Activate it
        Sync users in SLX Connect Users will be created in SLX Connect after authentication with LDAP
        Backup Authentication If LDAP credentials fail then user will be authenticated through SLX Connect
        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 SLX Connect 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

      19. Click on Save. After this, it will show you the list of User stores. Click on Test Configuration to check whether you have enter valid details. For that, it will ask for username and password.


      20. On Successful connection with LDAP Server, a success message is shown.
      21. Click on Test Attribute Mapping.
      22. Amazon Web Services(AWS) Single Sign-On (SSO) LDAP successful connection


      23. Enter a valid Username. Then, click on Test. Mapped Attributes corresponding to the user are fetched.


      24. After successful Attribute Mapping Configuration, go back to the ldap configuration and enable Activate LDAP in order to authenticate users from AD/LDAP.
      25. Refer our guide to setup LDAPS on windows server.


      2.2: Setup SLX Connect as a User Store

      1. Log in to SLX Connect Admin Console.
      2. There are 3 ways to setup SLX Connect as an Identity Source

        2.2.1 Create User in SLX Connect

        • Click on Users >> Add User.
        • Amazon Web Services(AWS) Single Sign-On (SSO)add user in SLX Connect


        • Here, fill the user details without the password and then click on the Create User button.
        • Amazon Web Services(AWS)Single Sign-On (SSO) add user details


        • After successful user creation a notification message "An end user is added successfully" will be displayed at the top of the dashboard.
        • Amazon Web Services(AWS)Single Sign-On (SSO) add user details


        • Click on On Boarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.
        • Amazon Web Services(AWS) Single Sign-On (SSO) email action


        • Now, Open your email id. Open the mail you get from SLX Connect and then click on the link to set your account password.
        • On the next screen, enter the password and confirm password and then click on the Single Sign-On (SSO) reset password button.


        • Now, you can log in into SLX Connect account by entering your credentials.

        2.2.2 Bulk Upload Users in SLX Connect via Uploading CSV File.

        • Navigate to Users >> User List. Click on Add User button.
        • Amazon Web Services(AWS) Single Sign-On (SSO)add user via bulk upload


        • In Bulk User Registration Download sample csv format from our console and edit this csv file according to the instructions.
        • Amazon Web Services(AWS) Single Sign-On (SSO) download sample csv file


        • To bulk upload users, choose the file make sure it is in comma separated .csv file format then click on Upload.
        • Amazon Web Services(AWS) Single Sign-On (SSO) bulk upload user


        • After uploading the csv file successfully, you will see a success message with a link.
        • Click on that link you will see list of users to send activation mail. Select users to send activation mail and click on Send Activation Mail. An activation mail will be sent to the selected users.

        2.2.3 Self User Registration

        • SLX Connect self user registration allows end users to register themselves using customized registration form. SLX Connect admin users can customize the registration form by adding more custom fields according to their choice. Follow the SLX Connect guide to customize user self registration page.

      Step 3: Setting SAML in Amazon Web Services (AWS)

      • Login to your Amazon Web Services (AWS) Consoleas an admin.
      • Click on Services Tab. Under Security, Identity & Compliances click on IAM (Identity and Access Management).
      • Amazon Web Services (AWS) SSO select IAM


      • From the left-hand side list, click on Identity Providers and then click on Create Provider button in the right section.
      Amazon Web Services (AWS) SSO click on create provider

      Step 4: Configure Provider in Amazon Web Services (AWS)

      • In the Configure Provider, select SAML as Provider type from the drop-down list.
      • Enter any Provider Name (e.g SLX Connect.
      • Click on Choose File button and choose a metadata file that you have already downloaded in Step 1, then click on Next Step.
      • Amazon Web Services (AWS)SSO configure provider


      • In the next screen, you will be shown your entered provider information. Verify it and click on the Create button. The SAML Provider is created and it should be listed in the Provider table.
      • Amazon Web Services (AWS) SSO SAML provider created


      • Now click on Roles from the left-hand side list and then click on Create role button.
      • In the Create Role section, click on SAML 2.0 federation tab.
      • Under Choose SAML 2.0 Provider, select the SAML Provider that you have created previously i.e SLX Connect.
      • SSO for AWS choose your saml provider


      • After that, choose Allow programmatic access only radio option.
      • Select SAML:aud option from the Attribute drop-down list.
      • Enter the value as https://signin.aws.amazon.com/saml.
      • Then, click on Next: Permissions button.
      • Check the Policy Name AmazonEC2ReadOnlyAccess and click on Next: Tags button.
      • Amazon Web Services (AWS) SSO check policy name


      • Then, skip Step Add Tags (Optional) by clicking on Next:Preview button.
      • In the next step, enter Role name and click on Create Role button.
      • Amazon Web Services (AWS) SSO create role


      • Click on your created role name.
      • In the Summary section, click on the Trusted relationship tab and copy Role ARN and Trusted Entities value.
      • Keep the values with you in comma separated format. For example- [arn:aws:iam::656620318436:role/SSORole,arn:aws:iam::656620318436:saml-provider/SLX Connect]
      • Amazon Web Services (AWS) SSO comma separated format role settings


      Step 5: Add attributes for AWS

      • Login to the SLX Connect Admin Console.
      • Then, Navigate to Apps >> Manage Apps. replica handbags
      • Configure the application that you have added.
      • Scroll down to the Attributes section, enter the value https://aws.amazon.com/SAML/Attributes/RoleSessionName in the Attribute Name field and select E-Mail Address from the Attribute Value list.
      • Click on the '+' icon besides Add Attributes to add another set of attributes and enter the value https://aws.amazon.com/SAML/Attributes/Role in the Attribute Name field, select Custom Attribute Value from the Attribute Value list and in the Custom Attribute Value, enter comma separated value that created in step 3 e.g. [arn:aws:iam::656620318436:role/SSORole,arn:aws:iam::656620318436:saml-provider/SLX Connect].
      • Amazon Web Services (AWS) SSO add attributes


      • If you have configured more than one role, you can enter additional attributes for them.

      Step 6: Login to your Amazon Web Services(AWS) account with SLX Connect IdP by either of the two steps:

        Using SP Initiated Login

        1. Go to your Amazon Web Services(AWS) URL, enter your credentials then click on Login. Now you will be redirected to SLX Connect IdP Sign On Page.


        2. Enter your SLX Connect login credential and click on Login. You will be automatically logged in to your Amazon Web Services(AWS) account.

        Using IDP Initiated Login

        1. Login to SLX Connect IdP using admin credentials and select the User Dashboard from the right side menu.


        2. Click on Amazon Web Services(AWS) application which you added, to verify your SSO configuration.

      Step 7: Adaptive Authentication with Amazon Web Services(AWS)

      7.1: Restricting access to Amazon Web Services(AWS) with IP Blocking

        You can use adaptive authentication with Amazon Web Services(AWS) 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:
      • Login to Self Service Console >> Adaptive Authentication.
      • Add a Policy Name for your Adaptive Authentication Policy.
      • Amazon Web Services(AWS) Single Sign-On (SSO) Restrict Access adaptive authnetication policy


      • Select your Action for behaviour Change and Challenge Type for user from the Action for behaviour Change Section.
      • Amazon Web Services(AWS) Single Sign-On (SSO) Restrict Access adaptive authentication behaviour change



        Action for behaviour Change Options :


        Attribute Description
        Allow Allow user to authenticate and use services if Adaptive authentication condition is true.
        Challenge Challenege 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.

        Challenge Type Options :

        Attribute Description
        User second Factor The User needs to authenticate using the second factor he has opted or assigned for such as
      • OTP over SMS
      • PUSH Notofication
      • OTP over Email
      • And 12 more methods.
      • 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 recieve a OTP on the alternate email he has configured threw Self Service Conolse. Once user provides the correct OTP he is allowed to proceed further.

      • Now Enable Enable IP Restriction option from the IP RESTRICTION CONFIGURATION section to configure custom IP range.
      • Amazon Web Services(AWS) Single Sign-On (SSO) Restrict Access adaptive authentication ip blocking


      • Select the Action you want to perform if the IP address is out of the range. i.e Allow, Challenge & Deny.
      • Specify the IP Address range for which you want above setting to reflect. You can add more than one IP Address ranges by clicking on following button +.
      • Scroll to the end and click on save.


      7.2: 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 wii be able to access services provided by us on this fixed no. of devices.

        You can cofigure Adaptive Authentication with Device Restriction in follwing way

      • Login to Self Service Console >> Adaptive Authentication.
      • Add a Policy Name for your Adaptive Authentication Policy.
      • Select your Action for behaviour Change and Challenge Type for user from the Action for behaviour Change Section.
      • Amazon Web Services(AWS) Single Sign-On (SSO) Restrict Access adaptive authentication behaviour and challenge type



      • Scroll down to Device Configuration section and enable Allow User to Register Device option to allow users to register their devices.
      • Enter the Number of Devices which are allowed to register in field next to Number of Device Registrations Allowed
      • Choose Action if number of devices exceeded (This will override your setting for Action for Behaviour Change.)
        1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 7.1
        2. Deny : Deny users access to the system
      • Enable option Send email alerts to Users if number of Device registrations exceeded allowed count if you want to alert the user about no of devices exceeding the limit. Save the configuration.
      • Amazon Web Services(AWS) Single Sign-On (SSO) Restrict Access adaptive authentication enable device restriction



      7.3: Add Adaptive Authentication policy to Amazon Web Services(AWS).

      • Login to Self Service Console >> Policies.
      • Amazon Web Services(AWS) Single Sign-On (sso) edit device restriction policy
      • Click on Edit option for predefined SAML app policy.


      • Set your application name in the Application and select password as Login Method.
      • Enable Adaptive Authentication on Policy page and select the required restriction method as an option.
      • From Select Login Policy dropdown select the policy we created in last step and click on save.
      • Amazon Web Services(AWS) Single Sign-On (SSO) Restrict Access save device restriction policy


        How to add a trusted Device
        1. When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

      More Secure authentication with Two-Factor Authentication

      The most practical way to strengthen authentication is to require a second factor after the username/password stage. Since a password is something that a user knows, ensuring that the user also has something or using biometrics thwarts attackers that steal or gain access to passwords.

      Traditional two-factor authentication solutions use hardware tokens (or "fobs") that users carry on their keychains. These tokens generate one-time passwords for the second stage of the login process. However, hardware tokens can cost up to $40 each. It takes time and effort to distribute them, tracks who has which one, and replace them when they break. They're easy to lose, hard to use, and users consistently report high levels of frustration with token-based systems.


      Your choice of the second factor

      SLX Connect authentication service has 15+ authentication methods.

      You can choose from any of the above authentication methods to augment your password based authentication. SLX Connect authentication service works with all phone types, from landlines to smart-phone platforms. In the simplest case, users just answer a phone call and press a button to authenticate. SLX Connect authentication service works internationally and has customers authenticating from many countries around the world.



      For Further Details:

      Creating SAML Identity Providers