Background

Some TrioFox clients may already be using Office 365/Azure AD and wish to use their Azure AD credentials for single sign-on to TrioFox. This article describes how a TrioFox user can be federated with an Azure AD such that Azure AD is the Security Assertion Markup Language (SAML) Identity Provider (IdP0 and TrioFox will be the SAML Relying Party (RP). These instructions require Azure AD Premium. 

Configuration

1. Sign in to the TrioFox server's management portal as a cluster administrator.
2. Click on Single Sign On:

3. Right-click the Link on the page to view the access service provider metadata and select open in a new tab:

4. The page will display xml with links needed for Azure AD:

• Locate the " md:EntityDescriptor entityID" URL in the XML data and copy the URL and paste it into a text editor similar to this:

  Identifier=https://tfdemo.hadroncloud.com/portal/saml2.aspx

• Locate the " md:AssertionConsumerService Location" URL XML data and copy the URL and paste it into a text editor similar to this:

  Reply URL=https://tfdemo.hadroncloud.com/portal/saml2.aspx

• Locate the "md:OrganizationURL" URL XML data and copy the URL and paste it into a text editor with a line similar to this:

  Sign on URL=https://tfdemo.hadroncloud.com/portal/LoginPage.aspx

5. Switch back to the tab with TrioFox and switch the toggle to On:

6. On the next page it will ask you to select your SSO provider. Choose Azure AD from the drop down list and click next:

7. At this point you will be prompted for your Azure AD Directory ID:

8. Open a new browser tab or window and navigate to https://portal.azure.com/. Sign in with your Azure AD (Office 365) credentials.

9. Click the hamburger menu icon in the top left of the page and select Azure Active Directory:

10. Click Enterprise applications in the new blade:

11. Click New application in the All applications window:

12. Click Non-gallery application in the Add an application blade:

13. Add some descriptive name for the new application then click the Add button at the bottom of the Add your own application blade:

14. Click the Single sign-on node in the Enterprise Application blade:

15. Click the SAML card:

16. Click the Edit (pencil) icon in the #1 Basic SAML Configuration section:

17. In the BASIC SAML Configuration blade:

• 1. Set the Identifier (Entity ID) text box to the Identifier text that was saved from the TrioFox XML Metadata (the "md:EntityDescriptor entityID" URL).
• 2. Set the Reply URL (Assertion Consumer Service URL) text box to the Reply URL text that was saved from the TrioFox XML Metadata (the "md:AssertionConsumerService Location" URL).
• 3. Set the Sign on URL text box to the Sign on URL text that was saved from the TrioFox XML Metadata (the " md:OrganizationURL" URL).
• 4. Leave the Relay State text box empty.
  
• 5. Click the Save icon at the top of the blade the close the blade.

18. In most cases it is not necessary to modify the User Attributes & Claims settings:

However, if the user's are signing into TrioFox with their mail address and it's different than their userPrincipalName, you could modify the Name attribute such that is uses user.mail as opposed to user.userprincipalname.

19. In the SAML Signing Certificate section click on the Federation Metadata XML link:

20. Save the FederationMetadata.xml file to your Downloads folder.
21. Click on Users and groups node in the Enterprise Application.
22. Add users or groups that should have access to the TrioFox app in Azure AD.

23. Go to the Overview page for your Application, here can see an 'Application ID' under properties. Copy this and save it somewhere to be used later on.
24. Close the Enterprise Applications blade.
25. Click on the Properties node of Azure Active Directory, then copy the Directory ID to the clipboard:

26. Switch back to the TrioFox portal.

27. Paste the Directory ID text from step 25 into the Directory ID box and paste the Application ID from step 23 into the Application Id text box and click next.

28. On the next page, you may want to have some descriptive text for the Display text for SSO link and disable the Add SSO link to login page. When finished click Commit:

29. You will then be brought to the screen showing Single Sign On is enabled:

Client Usage

Web Client

1. There are two methods to sign into TrioFox. The first is Identity Provider (IdP) initiated.
2. Navigate to https://myapps.microsoft.com. If you are using the same browser, you won't be prompted for sign in again.
3. Locate the TrioFox application you created and click on the app.
4. If you watch the address bar you will see some redirects but eventually you should be signed into the correct tenant in the TrioFox portal without being prompted for credentials.
5. The second method is Relying Party (RP) initiated.
6. Use the URL created on the XML generated by TrioFox:
   
7. You will see some redirects if you watch the address bar, including 'https://login.microsoftonline.com'. If you are using the same browser, you won't be prompted for credentials because your browser already has the token from the previous sign in to Azure AD. You should see the TrioFox portal page.

Windows Client

Install the Windows client as usual, that is, first sign into the web portal using the SSO relying party URL as described in the previous section, then download the Windows client software. After installation, the Windows client will use the security token from the web browser to sign the user in the first time. If the Windows Client signs out or the token expires, the Windows Client sign on dialog will be displayed. Click on the Azure AD Single Sign On link as seen in this screenshot to initiate the Azure AD sign on process in the browser:

Android Client

When setting up the Android client, type in the TrioFox server end point and user name on the first screen, then in the password screen press or Login with: Single Sign On as seen in this screenshot to start the Azure AD sign on process. 

Troubleshooting

See this article: Troubleshooting SAML single sign on