-
I am accessing this url and it gives me below error:

PS: There are many tutorials here including an example OIDC set up for Okta:
https://code.onedev.io/projects/162/blob/main/pages/tutorials.md
-
Thanks Robin,
Could I ask which URL you're getting that error from? I just hit the pasted URL from a completely disconnected device, one that has never logged in to this site at all, and got this:

I was actually following that guide when I ran in to this issue, so just trying to figure out what may be blocking.
-
In the meantime, I'm going to dig through CloudFlare to see if there's something there to assist as well.
-
I am accessing this url:
https://auth.unseenspite.com/application/o/git/.well-known/openid-configuration
Either accessing from browser (with cache cleared and start clean) or with curl gives me same result.
-
Scratch everything I just asked. It's a combination of none of the services actually being secure (behind reverse proxy but only for base 80/443) and CloudFlare being over jealous on it's defense. I will fix and it will likely work just fine. Please feel free to close the ticket.
Edit: Removed screenshot since CloudFlare data was included.
-
Previous Value Current Value Open
Closed
-
Closing now. Feel free to reopen if you have any problems configuring OneDev working with Authentik
-
Unfortunately, I am back with more issues. I got the two servers talking successfully, but immediately get an error of:
OIDC response error (code: invalid_grant, description: The provided authorization grant or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client, http status code: 400)
Unfortunately, neither server seem to be logging any errors at all regarding this one, so I'm a bit stuck how to begin digging in to what the actual issue is. Any advice on where to start debugging would be greatly appreciated.
-
And yet again, this one was completely on a bad build. I ripped this back down and rebuilt it from scratch and everything works great. Apparently, somehow (still haven't figured out how I did it), the time on the OneDev server wasn't synced properly, so the token times didn't match. Very odd, but a rebuild is all that was needed.
-
Glad to see it is working now.
| Type |
Question
|
| Priority |
Normal
|
| Assignee |
I cannot find generic instructions for connecting OIDC, but as far as I can tell, I have this set up correctly - however, clicking on the OpenID button on login is giving an error of
Visiting this URL, however, does in fact return valid information (it is public facing). I am trying to debug to figure out where the issue is actually occurring. I am able to validate that the data from the configuration page does in fact return and that (so far) I have no error logs on the authentication server.
Logs from OneDev show:
Current setup for OneDev:
Current setup for Auth Server: