SSO for Azure portal (Microsoft)

This document aims to assist the subscriber to enable and setup the SSO for the Skedway application on the Microsoft Azure portal.

This document may be out of date due to constant changes that Microsoft makes on the Azure portal. Microsoft does not notify you of changes made.

Adiciontal informations

• For these configurations, the user must have the appropriate access permissions within Microsoft Azure Portal.

• Necessary a Azure AD subscription.

• Skedway subscription with SSO feature.

Initial setup

The SSO setup will start with sending the xml certificate by the Skedway team to the customer. Upon receipt, the customer must configure them within the Azure portal.

Below is a step by step on how to do this.

Creating a Skedway aplication in Azure portal

Accessing the Azure portal and creating your own application:

1. Sign in with your Azure Portal and access the Enterprise Applications.

2. Select Add an application and then Add your own application. In the displayed options, define as: "Integrate any other application you don`t find in the gallery". This may take a few minutes.

3. On save, select the SAML-based Signon option.

Set up Single Sign-On with SAML

1. In the newly created Skedway application, on the Basic SAML Configuration, upload the xml file sent by the Skedway team, and make sure the access urls were added after uploading the file on item 1.

   1. Identifier (Entity Id)

   2. ReplyURL (Assertion consumer service URL).

      

      

Note: If you don't have the url data, fill in some provisional, temporary url. You will update these fields later after Skedway team get back to you with the correct URLs.

Configuring the Attributes and Claims

1. On the User Attributes & Claims, item 2, make sure the following parameters are as follows below by clicking on the Edit icon:

   1. givennname: user.givernname

   2. surname: user.surnamer

   3. emailaddress: user.mail

   4. name: user.userprincipalname

   5. Unique User Identifier: user.mail

      

      
2. Make sure that the Required claim > Claim name > Unique Udentifier (name ID) parameter is set to user.mail, as illustrated in the images below, and Save.

   

   

   Image illustrated parameter change

Download Federation Metadata

Go to item 3- SAML Signing Certificate and download the Federation Metadata XML file and send it to the Skedway team. They will complete the SSO setup on the system.

User access

After the configuration is completed, it is necessary to define the users or groups of users that will be able to access the SAML application for the SSO to work. Without adding users, when a collaborator logs into the Skedway, he will receive an error message.

Test & Validation

After configuring the Skedway side, it is common for the customer to provide a test user for Skedway to verify that everything has been configured correctly. If the customer does not have a test user, he will need to test with a real user account.

Support

If you have any question regarding this topic, please contact our support team.

E-mail: [e-mail] Skedway service desk portal: Click here!

Skedway