Page Comparison

This article covers connecting the Foray ADAMS solution to an Azure Active Directory (AD) domain. This connection allows users to login to the Foray ADAMS solution and also allows Foray ADAMS to perform queries necessary to enforce privileges for both data and features.

...

1. Open the Azure Portal

2. Navigate to Azure Active Directory

3. App registrations

4. New registration

5. Name - Foray Adams Web, Foray Adams Admin, or Foray Adams Clients
   
   This name is visible to end users. You may use a different name if you chose. If so you will need to identify that name later in these steps. You can change this name later.
   

6. Supported account types: Accounts in this organizational directory only

7. Redirect URI

   Select a platform - Web

   1. Adams Admin

      1. This URL will be provided by Foray. It will be similar to:
         Example

         Code Block
         https://web01.myagency.foray.com/AdamsAdmin/Account/Login

   2. Adams Web

      1. This URL will be provided by Foray. It will be similar to:
         Example

         Code Block
         https://web01.myagency.foray.com/AdamsWeb/Login.aspx

   3. Adams Clients

      1. Select "Public client/native (mobile & desktop)" from the dropdown

         1. Enter the value: https://login.microsoftonline.com/common/oauth2/nativeclient

   Platform configurations

   1. Adams Web

      Code Block

      language	xml

      Ex1: https://web01.myagency.foray.com/AdamsAdmin/Account/

      1. Web - Redirect URI - This URL will be provided by Foray. It will be similar to:
         Example

         Code Block
         https://web01.myagency.foray.com/AdamsWeb/Login.aspx

      2. Single-page application

      3. Click Add a platform

      4. Select Single-page application

      Enter the Redirect URI

      provided by Foray. It will be similar to:
      Example

      Code Block
      https://web01.myagency.foray.com/AdamsWeb/

      ApiRedirect.html

      5. If prompted, choose to migrate the URI for use with SPA and MSAL.js 2.0

      For Adams Admin - This is the URL provided by Foray for redirect. It will be similar to:
      For Adams Admin and Adams Web - This is the URL provided by Foray for redirect. It will be similar to:

      Examples

      1. Login

      Ex2: https://web01.myagency

      1. .

      foray.com/AdamsWeb/Login.

      1. aspx

   2. For Adams Clients

      1. Select "Public client/native (mobile & desktop)" from the dropdown

         1. Enter the value: https://login.microsoftonline.com/common/oauth2/nativeclient

   3. Click Register

   Complete the below steps for the current app before starting with the next app

Configure Authentication

Perform these steps for each of the applications registered.

1. Select the application to be configured

2. Authentication

3. For Adams Admin

   1. Front-channel Logout URL

      1. This URL is provided by Foray for logout. It will be similar to:

         Example

         Code Block
         language xml
         https://web01.myagency.foray.com/AdamsAdmin/Account/AzureSingleSignOut

   2. Implicit grant and hybrid flows - check ID Tokens

4. For Adams Web

   1. Click Add a platform

      1. Select Single-page application

      2. Enter the Redirect URI provided by Foray. It will be similar to:
         Example

         Code Block
         https://web01.myagency.foray.com/AdamsWeb/ApiRedirect.html

      3. If prompted, choose to migrate the URI for use with SPA and MSAL.js 2.0

   2. Front-channel Logout URL

      1. This URL is provided by Foray for logout. It will be similar to:
         Example

         Code Block
         https://web01.myagency.foray.com/AdamsWeb/Logout.aspx

   3. Implicit grant and hybrid flows

      1. Check Access tokens

      2. Check ID tokens

5. Supported account types: Accounts in this organizational directory only

6. Allow public client flows - Enable the following mobile and desktop flow

   1. Adams Admin and Adams Web: NO

   2. Adams Clients - YES

7. Click Save

...