Configure and test Microsoft Entra SSO for Samsara
Configure and test Microsoft Entra SSO with Samsara using a test user called B.Simon. For SSO to work, you need to establish a link relationship between a Microsoft Entra user and the related user in Samsara.
To configure and test Microsoft Entra SSO with Samsara, perform the following steps:
Browse to Identity > Applications > Enterprise applications > Samsara > Single sign-on.
On the Select a single sign-on method page, select SAML.
On the Set-up single sign-on with SAML page, click the pencil icon for Basic SAML Configuration to edit the settings.
On the Basic SAML Configuration section, perform the following steps:
a. In the Sign-on URL text box, type a URL using one of the following patterns:
https://cloud.samsara.com/signin/<ORGID> for US cloud customers
https://cloud.eu.samsara.com/signin/<ORGID> for EU cloud customers
b. In the Identifier (Entity ID) text box, type a URL using the following pattern:
urn:auth0:samsara-dev:samlp-orgid-<ORGID>
c. In the Reply URL text box, type a URL using the following pattern:
https://samsara-dev.auth0.com/login/callback?connection=samlp-orgid-<ORGID>
Note
These values are not real. Update these values with the actual Sign-on URL, Reply URL, and Identifier. Contact the Samsara Client support team to get these values, or in Samsara, go to Settings > Single-Sign-On > New SAML Connection to obtain the <ORGID>. You also can refer to the patterns shown in the Basic SAML Configuration section.
On the Set-up single sign-on with SAML page, in the SAML Signing Certificate section, find Certificate (Base64) and select Download to download the certificate and save it on your computer.
On the Set-up Samsara section, copy the login URL
Create a Microsoft Entra test user
In this section, you'll create a test user called B.Simon.
Browse to Identity > Applications > Enterprise applications > Samsara.
In the app's overview page, select Users and groups.
Select Add user/group, then select Users and groups in the Add Assignment dialog.
In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
In the Add Assignment dialog, click the Assign button.
Configure Samsara SSO
To configure single sign-on on Samsara side, you need to send the downloaded Certificate (Base64) and Login URL from Azure portal to Samsara support team. They set this setting to have the SAML SSO connection set properly on both sides.
Create Samsara test user
In this section, a user called B.Simon is created in Samsara. Samsara supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in Samsara, a new one is created after authentication with a default role of Standard Admin (No Dash Cam Access) for Organization. The user's access can then be increased or decreased as needed in Samsara.
Test SSO
In this section, you test your Microsoft Entra single sign-on configuration with following options.
SP initiated:
Click on Test this application, this will redirect to Samsara Sign on URL where you can initiate the login flow.
Go to Samsara Sign-on URL directly and initiate the login flow from there.
IDP initiated:
Click on Test this application, and you should be automatically signed in to the Samsara for which you set up the SSO.
You can also use Microsoft My Apps to test the application in any mode. When you click the Samsara tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Samsara for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.
Deploying and monitoring enterprise applications to Azure solutions can ensure security. Explore how to deploy on-premises and cloud based apps to users.