Skip to content
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

Auth OIDC and Gitlab errors, but nothing in logs #154

Closed
nathanael-h opened this issue Apr 4, 2022 · 5 comments · Fixed by #155
Closed

Auth OIDC and Gitlab errors, but nothing in logs #154

nathanael-h opened this issue Apr 4, 2022 · 5 comments · Fixed by #155
Labels
bug Something isn't working go Pull requests that update Go code

Comments

@nathanael-h
Copy link

Hello,
I am trying to configure OIDC or Gitlab auth.
The point is that I have for both I end with an error like this on web:

server error
trace = 060dd72d-2072-40a2-8ea3-xxxxxxxxxxxx

But even with log level set to DEBUG I have nothing in the logs output of the wg-access-server container.

So do you think I could have more logs to understand what is the error I have? Or maybe do you see any bad config I made?

Here is my config.yaml

auth:
  oidc:
    name: "SSO CAS"
    issuer: "https://sso-preprod.aaa.fr/cas/oidc"
    clientID: "wireguard"
    clientSecret: "xxx"
    scopes:
      - openid
      - profile
      - email
    redirectURL: "https://vpn.aaa.fr/callback"
    claimMapping:
      admin: "'WireguardAdmins' in group_membership"
  gitlab:
    name: "Gitlab Preprod"
    baseURL: "https://git.aaa.fr"
    clientID: "xxxxxx"
    clientSecret: "yyyyyyy"
    redirectURL: "https://vpn.company.fr/callback"
    emailDomains:
      - aaa.fr
@DasSkelett
Copy link
Member

Yeah, the missing logs for grpc endpoints was to be fixed with #119, but I think I'm going to split that out into a separate PR now since I've got some code for this already.

@DasSkelett DasSkelett added bug Something isn't working go Pull requests that update Go code labels Apr 4, 2022
@nathanael-h
Copy link
Author

nathanael-h commented Apr 4, 2022

Ok, sorry I saw this PR, and I thought it was something different. If you need me to test some PR about this I can try . By the way, do you see any issue with my config file?

@DasSkelett
Copy link
Member

If you are setup for building the binary or Docker image from source you can try #155, I would welcome testing and feedback.
The config looks good to me, syntax-wise. Could be that wg-access-server can't reach the Issuer, but also anything else.

@nathanael-h
Copy link
Author

Hello, the problem was on the OIDC server that was not sending a namevalue. We have been able to fix this on our side thanks to the logs provided via #155 😎 👍

@DasSkelett
Copy link
Member

Nice to hear! I've also added a commit to #155 to handle a missing name gracefully, it's not needed and only optional for the "All Devices" list (where it falls back to the email address or subject).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working go Pull requests that update Go code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants