You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm trying to use the library to authenticate a wso2 custom service provider.
To achieve this goal I've started following the official documentation so I've created an application in Asgardeo console and so more.
My problem is this one:
In development mode I can correctly finish the authentication flow both with asgardeo application or with our custom wso2 provider and have a valid access token;
In production mode (deploy on a server), with wso2 or asgardeo app there is no difference, when I complete the auth flow and get back to my callback url I have to click on login button once more to call the /token api and obtain a valid access token but obviusly the source code is the same.
I like to specify that if I'll run my app with serve library all works correctly. It's only when the webapp is hosted by the server.
What could be the problem?
Here my auth json
{
"clientID": my client id,
"serverOrigin": wso2 or asgardeo,
"signInRedirectURL": my webapp,
"signOutRedirectURL": my webapp,
"storage":"webWorker",
"resourceServerURLs": [backend wso2 api],
"validateIDToken": false
}
The text was updated successfully, but these errors were encountered:
Hello,
I'm trying to use the library to authenticate a wso2 custom service provider.
To achieve this goal I've started following the official documentation so I've created an application in Asgardeo console and so more.
My problem is this one:
I like to specify that if I'll run my app with serve library all works correctly. It's only when the webapp is hosted by the server.
What could be the problem?
Here my auth json
{
"clientID": my client id,
"serverOrigin": wso2 or asgardeo,
"signInRedirectURL": my webapp,
"signOutRedirectURL": my webapp,
"storage":"webWorker",
"resourceServerURLs": [backend wso2 api],
"validateIDToken": false
}
The text was updated successfully, but these errors were encountered: