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

don't use private_key_jwt if no private keys are configured #189

Closed
zandbelt opened this issue Oct 27, 2016 · 1 comment
Closed

don't use private_key_jwt if no private keys are configured #189

zandbelt opened this issue Oct 27, 2016 · 1 comment

Comments

@zandbelt
Copy link
Member

When a provider indicates support for token endpoint authentication method private_key_jwt the modules should only pick this method over others if private keys have been configured. See also:
Reposoft/openidc-keycloak-test#6
@zandbelt zandbelt mentioned this issue Oct 27, 2016
Merged
@solsson
Copy link

solsson commented Oct 27, 2016 •
edited

I will verify by removing the directive again in the PR, later today and once the rc7 source tarball is up once a new rc source is downloadable. My builds there can't pull directly from git.

Update again: no need to make source tarballs. I can download https://github.com/pingidentity/mod_auth_openidc/archive/3ee2ffb2ce4aef9840882d3dc2252110ae05d591.tar.gz

solsson added a commit to Reposoft/openidc-keycloak-test that referenced this issue Oct 27, 2016
@solsson
Confirms fix of OpenIDC/mod_auth_openidc#189 by reverting to automati…
b0b30fe 
…c endpoint auth selection
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

No branches or pull requests
2 participants
@solsson @zandbelt