TABLE OF CONTENTS

• Azure Ad Authentication Connector
• Service token authentication Connector
  • Generating the service account token
  • Creating the connector
  • Testing connector
  • Probable reasons for failed test

Azure Ad Authentication Connector

1. Go to IDE web
2. Make sure the user has tenant setup role assigned
3. Go to connector → new connector select Ilap Analytics from dropdown. Select AzureAd Signin as authentication type

The values to be put here are

• Authority: ‘https://login.microsoftonline.com/[YourTenantId]/v2.0’
• ClientId: Client Id of the analytics ui app registration
• Scopes: [Application Id URI of the analytics API app registration]/user_impersonation User.Read offline_access

A sample configuration could look like below Note that copying the example without changing it won’t work

• Authority: “https://login.microsoftonline.com/e8ddb777-121f-4abc-a113-6b91d4b5dafc/v2.0”,
• Scopes: “api://5f9d20ce-8ac7-4115-80a7-2f1baacd7bda/user_impersonation User.Read offline_access”,
• ClientId: “b680058e-860b-4acc-80cb-89f8a1fd5a99”

If you don’t have access to your organization’s IT infrastructure, ask your it team (preferrably the person who setup ILAP Analytics in your organization) the following questions

1. What is your organization tenant ID
2. What is the Client id of the analytics ui app registration
3. What is the application ID URI for the analytics api app registration

Service token authentication Connector

Generating the service account token

1. Log in to Ilap Analytics web ui.
2. Go to Admin → Generate new token → put the token name and set the expiry date
3. Copy the generated token

Service token

Creating the connector

1. Go to IDE web
2. Make sure the user has tenant setup role assigned
3. Go to connector → new connector select Ilap Analytics from dropdown. Select “Service Account Token” as authentication type. and put the service token generated previous section as service account token.

Testing connector

1. log in to IDE desktop client.
2. Navigate to the connector page.
3. Click Test on the connector that you just created. In case of Azure AD authentication, a desktop browser might open wher you have to put your Azure AD credentials.
4. In case of successful setup, the test will be successful and a success message will be shown like the picture below.

Probable reasons for failed test

• The desktop application user might not have network access to the Ilap Analytics API.
• The analaytics api might not be up and running

• The connector was not properly configured with proper Azure ad configs.

• The user might not have sufficient permission to access this app.