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.

Sign up for GitHub

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

Jump to bottom

Verification failed if client signing algorithm is string #57

Open
iconoeugen opened this issue Jul 11, 2016 · 0 comments · May be fixed by #58
Open

Verification failed if client signing algorithm is string #57

iconoeugen opened this issue Jul 11, 2016 · 0 comments · May be fixed by #58

Comments

@iconoeugen
Copy link

While configuring Gitlab to use openid-connect for SSO without discovery, the in values for omnibus are provided as yaml. The values from yaml are interpreted in ruby as strings and not as symbols, but the check in the key_or_secret function is done against symbols, which leads to a verification failure:

** [Raven] Event not sent due to excluded environment: production

JSON::JWS::VerificationFailed (JSON::JWS::VerificationFailed):
  lib/gitlab/middleware/go.rb:16:in `call'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Convert client_signing_alg to symbol in key_or_secret.
1 participant
@iconoeugen