-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication error: Mismatching redirect uri #200
Comments
I experience the same thing : |
Fixed in mashlib 1.8.8 through the issues mentioned above. Thanks @bourgeoa ! |
Hi. Is this included in the standalone web version of mashlib (https://solidos.github.io/mashlib/dist/browse.html) as well? |
Yes there is only one mashlib build. |
I tried to do, but did not manage so. In particular, I cannot get rid of this error message now. I do not have cookies nor local storage for Mashlib (https://solidos.github.io/mashlib/dist/browse.html) and solidcommunity.net. But I do get this issue every time now. A plausible guess is: I log-in with solidcommunity.net first with Mashlib; then log-out; then log-in with another Solid account (my own CSS host); then log-out; then trying to log-in to solidcommunity.net -- problem appeared. Not sure though. Will try more. |
Using solidcommunity.net with Node Solid Server 5.7.4 (mashlib 1.8.5)
Not sure which component this behaviour comes from:
As intended, solidos tries to login again.
Error occurs in the authorize step:
https://solidcommunity.net/authorize?client_id=eaabc2c1e05114db2327794f34f54f56&redirect_uri=https%3A%2F%2Fjosephguillaume.solidcommunity.net%2F%3Fstate%3D2d8634d1ec034756882cb299fc60ef38&response_type=code&scope=openid%20offline_access%20webid&state=176ab065bec548dbaf188b765d4f28d2&code_challenge=IJAMzeDfoBcwdWIj0pvVdmSVvtjQdGz_f2bPO-3auvY&code_challenge_method=S256&prompt=none&response_mode=query
{"error":"invalid_request","error_description":"Mismatching redirect uri"}
The error seems to be due to the added state parameter in the redirect URI.
The text was updated successfully, but these errors were encountered: