| ulm: choose this to configure Vindicia IDP | The following fields are relevant: | |
| - JSON Web Key (JWK) Endpoint URL: JWKS is a set of keys containing the public keys used to verify any JSON Web Token (JWT) issued by the authorization server. It must exactly match the redirect URIs that is registered in ulm. Note: Receive this from the ticket user mapping ticket for opened for ulm | Example value: https://merchantportal.m1amdocs.com/oidc/jwkThe <merchantportal> section provides a different entry for each merchant. | |
| - Authorization Endpoint: To grant access, Vindicia accepts an authorization code. The authorization endpoint interacts with the Resource Owner and obtain an Authorization Grant. It must exactly match the authorization endpoint created and registered in ulm. Note: Receive this from the user mapping ticket opened for ulm | Example value: https://merchantportal-ulm-pdt.m1amdocs.io/oidc/authorizeThe <merchantportal> section provides a different entry for each merchant. | |
| - Token Endpoint: The token that can make requests to the resource. By posting a request to the /token endpoint, the user gets the access token. Note: Receive this from the user mapping ticket opened for ulm | Example value: https://merchantportal-ulm-pdt.m1amdocs.io/oidc/tokenThe <merchantportal> section provides a different entry for each merchant. | |
| - Client ID: Client (merchant) identifier that must exactly match with the one generated in ulm. Note: Receive this from the user mapping ticket opened for ulm | Example value: e0c7390484ae45b999dc7525be9327be | |
| - Password Reset Link: Merchant’s IDP User Management Portal URL in which the user can update login details. Note: Receive this from the user mapping ticket opened for ulm - Tenant URL | Example value: https://merchantportal-ulm-pdt.m1amdocs.io/ | |
| - Client Secret: IDP configuration Secret generated by ulm. Once entered, it is masked for viewing for security purposes. Note: Receive this from the user mapping ticket opened for ulm | Example value: asd1d1d121dasd12e321dasd | |
| ULM M2M API Configuration | Machine-to-Machine API details are needed in order to add new users for the merchant once. Users are added in the Vindicia portal and sent automatically to ulm via API for creation.The following fields are relevant: | |
| - M2M Client ID: Client ID for the M2M API call, generated by ulm. Note: Receive this from the user mapping ticket opened for ulm | Example value: asd1d1s581dasd12e321dasd | |
| - M2M Client Secret: Client Secret for the M2M API call, generated by ulm. Once entered, it is masked for viewing for security purposes. Note: Receive this from the user mapping ticket opened for ulm | Example value: asd1d1s581dasd12e321dasd | |
| - M2M Tenant Link: Base URL for the API Call. Note: Receive this from the user mapping ticket opened for ulm | Example value: https://merchantportal-ulm-pdt.m1amdocs.io/ | |
| okta: choose this to configure Okta IdP. You will need to receive details from the merchant (MAC). | The following fields are relevant: | |
| - JSON Web Key (JWK) Endpoint URL: JWKS is a set of keys containing the public keys used to verify any JSON Web Token (JWT) issued by the authorization server. It must exactly match the redirect URIs that is registered in Okta. | Example value: https://merchant.okta.com/oauth2/ausmk34oz2PZAdU1i0x7/v1/keys | |
| - Authorization Endpoint: To grant access, Vindicia accepts an authorization code. This is the initial call that Vindicia would make when a user tries to log in.The authorization endpoint interacts with the Resource Owner (okta) and obtains an Authorization Grant. It must exactly match the authorization endpoint created by merchant in OKTA. | Example value: https//merchant.okta.com/oauth2/ausmk34oz2PZAdU1i0x7/v1/authorize | |
| - Token Endpoint: This is the path that Vindicia will use to validate the token. The token can make requests to the resource. By posting a request to the /token endpoint, the user gets the access token. | Example value: https://merchant.okta.com/oauth2/ausmk34oz2PZAdU1i0x7/v1/token | |
| - Client ID: Client (merchant) identifier that must exactly match with the one generated by the merchant in the Okta app. Note: Different Client ID may be provided for the Merchant’s Staging and Production environments in Okta | Example value: 0oa1qmrashpgBdtcq2d7 | |
| - Password Reset Link: Merchant’s IDP User Management Portal URL in which the user can update login details. | leave blank if not available | |
| - Client Secret: IDP configuration Secret (password) generated by merchant in the okta app. Once entered, it is masked for security purposes. Note: Different Client ID may be provided for the Merchant’s Staging and Production environments in Okta | | |
| azure: choose this to configure MS Azure | The following fields are relevant: | |
| - JSON Web Key (JWK) Endpoint URL: JWKS is a set of keys containing the public keys used to verify any JSON Web Token (JWT) issued by the authorization server. It must exactly match the redirect URIs that is registered in Azure. | Example value: https://login.microsoftonline.com/c3eca3ca-1246-46d5-4d2d-a0f2a028920f/discovery/v2.0/keys | |
| - Authorization Endpoint: To grant access, Vindicia accepts an authorization code. This is the initial call that Vindicia would make when a user tries to log in.The authorization endpoint interacts with the Resource Owner (azure) and obtains an Authorization Grant. It must exactly match the authorization endpoint created by merchant in MS Azure. | Example value: https://login.microsoftonline.com/c8eca3ca-1246-46d5-4d2d-a0f2a028920f/oauth2/v2.0/authorize | |
| - Token Endpoint: This is the path that Vindicia will use to validate the token. The token can make requests to the resource. By posting a request to the /token endpoint, the user gets the access token. | Example value: https://login.microsoftonline.com/c8eca3ca-1246-46d5-4d2d-a0f2a028920f/oauth2/v2.0/token | |
| - Client ID: Client (merchant) identifier that must exactly match with the one generated by the merchant in the Azure. Note: Different Client ID may be provided for the Merchant’s Staging and Production environments in MS Azure | Example Value: e0c2290484ae45b399dc7525be9327be | |
| - Password Reset Link: Merchant’s IDP User Management Portal URL in which the user can update login details. | leave blank if not available | |
| - Client Secret: IDP configuration Secret (password) generated by merchant in the Azure. Once entered, it is masked for security purposes. | | |
| Parent topic:Configuring Merchant Authentication with Vindicia IDP 1.0 and User Definition | | |