Configured authenticated web messaging with azure Ad but as soon as
POST /api/v2/webdeployments/token/oauthcodegrantjwtexchange endpoint is hit it returns 401 status code along with message "Failed to identify user for token ...", payload for that request is as shown below in image and below code is continuously executed making the /api/v2/webdeployments/token/oauthcodegrantjwtexchange endpoint to be hit multiple times.
AuthProvider.registerCommand("reAuthenticate", (e) => {
document.getElementById("authLoginBtn").click();
e.resolve();
});
The code to exchange looks suspicious.
It looks like a JWT format.
This is usually an opaque string.
I would first advise to double check this input.
Can you provide a contextId for the request(s) you made (by checking the headers tab) ?
From there, I can check corresponding logs.
invalid_client (AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app '<redacted>'. Trace ID: 6f79699d-e5dd-49f5-b31d-4bcbc2e3cf00 Correlation ID: a5945843-a8a7-432e-9ce7-fa1ee1b0a801 Timestamp: 2024-07-01 07:05:06Z)
Make sure to use the secret value in the request, not the secretID:
Hello @vpirat ,
Upon logging in using microsoft and on successful authentication, we can see customer details like name and other information in the interactions on Genesys Cloud when a message is sent through web messaging. Similarly, if I have a custom website with customer login details stored in a database, how can I authenticate this user in Genesys as well, so that the customer's details are passed to Genesys in the interactions?
Because here the problem is customer must have microsoft account in order to authenticate self, we want to create a scenario where there is no need to login using microsoft account but customer logins using id and password stored in database and then too user is authenticated and details are passed over to Genesys
This should be the Brand's authentication server. Hence it is assumed that users are already set-up.
Currently, we do support only OpenId framework. Doesn't mean it has to be Microsoft.
Any OpenId provider will do, and there are plenty of them:
AWS Cognito, Okta, Auth0, Google, Forgerock, etc.
Could you plug the OpenID provider with your existing database ?
Some of our customers developed their own OpenId provider as well.
Alternatively, feel free to submit an idea with your use case so that it can be shared with the community and reviewed by the product team.
Hi @vpirat ,
Do you have any details regarding developing own OpenId provider to get started with? Because I tried but not able to find any way out for creating own OpenId provider.
