SAML Federated Authentication is only available in the Mender Enterprise plan. See the Mender plans page for an overview of all Mender plans and features.
This example will show you how to set AWS IAM Identity Center as an Identity Provider (IdP) for hosted Mender as a Service Provider (SP).
∏
Go to your hosted Mender account in another browser tab to set up Mender as a SAML 2.0 Service Provider (SP). This step requires uploading the SAML metadata we downloaded in the previous section in the "Organization and billing" settings view, selecting SAML as Single Sign-On type.
Once the XML metadata file upload is complete, you will obtain the following information:
Please note these values and return to the other browser tab where you were setting up the AWS customer-managed SAML 2.0 application in the IAM Identity Center.
As Mender looks up users using their email address, we must ensure that AWS IAM Identity Center uses the email address as NameID format. To do so, we click on the "Edit attribute mappings" item from the "Actions" menu in the application details view:
In this screen, we set the "Subject" user attribute to the value ${user:email}
with format emailAddress
, and we click on "Save changes".
Please note that this setting depends on the underlying Identity Provider configured for your AWS account. Please refer to the AWS documentation available by clicking on the "Learn more" link on this page to define the correct value for your specific setup.
At this point, we need to replace the AWS IAM Identity Center metadata in Mender. To do so, click the "Edit configuration" item from the "Actions" menu in the application details view. We then scroll down to the "IAM Identity Center metadata" section and click on the "Download" link for the "IAM Identity Center SAML metadata file" field.
The newly downloaded XML will have the following line in it:
<md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</md:NameIDFormat>
Lastly, we can proceed to replace the SAML metadata file in hosted Mender in the "Organization and billing" settings view, as explained above. Please note that the Mender's SAML values (Start URL, ACS URL, Entity ID) won't change after you successfully upload the new SAML metadata file.
You must assign users and/or groups to the application to grant them access to hosted Mender. You can do so by clicking the "Assign users and groups" button in the application's detail view.
Please note that to enable users to access your tenant on hosted Mender, you have to create that user with the email address corresponding to the email set in the AWS IAM Identity Center. Ensure no password is set during user creation in Mender; otherwise, the SAML integration will be rejected.
At this point, Mender's integration with AWS IAM Identity Center is complete, and you can access your hosted Mender account from the AWS access portal. You can click the "Dashboard" link in the sidebar to obtain the AWS access portal URL and open it in a new tab.
From the AWS access portal, you will see hosted Mender in the list of "Applications". To initiate the session, click on the application and proceed with the authentication.
For further information, you can refer to the AWS documentation about how to Set up customer-managed SAML 2.0 applications.
© 2024 Northern.tech AS