Repository navigation
Replies: 1 comment
|
I got it sorted out. It appears the method Warpgate uses changed between 0.28.4 and 0.28.5. The above error was coming from Authelia, not Warpgate. I had to make the following change in Authelia's config: Restarted Authelia. Warpgate 0.28.4 was then no longer able to authenticate. I updated to 0.28.6 and it is working. Also, the new RDP option to force users to login again is very nice. Thank you! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Updated from 0.28.4 to 0.28.5 this morning and tried to login and I get to the end of the auth process and get this:
code verification error: invalid_client: Some("Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).
The request was determined to be using 'token_endpoint_auth_method' method 'client_secret_post', however the OAuth 2.0 client registration does not allow this method.")
Using Authelia. No other changes than the patched version and going back to 0.28.4 resolves the issue. I won't be able to dig further till this afternoon, but wanted to put this out there in case others are having the issue.
Thanks!
All reactions