Working Process with MSAL Authentication Provider

1. After logging into the Kuika platform, open the “Configuration Manager” module.
2. In the window that opens, name the configuration you want to create.

3. The App Setting tab will appear by default.

‍

4. Select a predefined configuration from the MSAL options in the “Authentication & Authorization” section of App Settings or create a new one with “ADD NEW”.

Content added by Global Config in Workspace is shown as read-only or hidden (*****) by other users who are not authorized to access it.

5. After creating a new one, you can make changes in the following fields from the MSAL Setting pop-up:

• Name: It is used to identify the added authentication provider. Users can give a meaningful name to the providers they add for easier identification.
  
• Client ID: The unique ID of the application created through the Azure portal. Client ID allows the application to be recognized by Azure AD (Active Directory).
  
• Client Secret: A secret key used to authenticate the application. The Client Secret key is used to verify that the application is an authorized application and should be kept secret.
  
• Authority: Enter the URL extension used for user authentication. For example; “https://login.microsoftonline.com/{tenant} or https://login.microsoftonline.com/common/.”
  
• Scopes: Permissions that specify which resources the application requests access to. For example, a scope like user.read grants permission to read the user's profile information.
  
• Keystore Base64: Usually used for Android applications and is the keystore obtained from the signed APK file of the application encoded in Base64 format.
  
• Cache Location: Use a switch to specify the location where authentication credentials and tokens are stored.  The switch controls whether the cache is turned on or off.
  
• Keystore Hash (Android only): Can be either SHA-1 or SHA-256 hash obtained from the signed APK file, only required for Android apps.