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

Error: no client authentication mechanism provided #84

Closed
MatthiasGrandl opened this issue Apr 10, 2020 · 3 comments
Closed

Error: no client authentication mechanism provided #84

MatthiasGrandl opened this issue Apr 10, 2020 · 3 comments

Comments

@MatthiasGrandl
Copy link

After logging in I get no client authentication mechanism provided. I use oidc-provider with the following client:

{
      client_id: "foo",
      client_secret: "bar",
      token_endpoint_auth_method: "client_secret_post",
      redirect_uris: ["http://localhost:3000", "http://localhost:3000/callback"],
      grant_types: ["authorization_code", "refresh_token"],
      response_types: ["code"]
}

This is my auth config:

{
    clientID: "foo",
    clientSecret: "bar",
    authorizationParams: {
      response_type: 'code',
      response_mode: 'form_post',
      scope: 'openid email offline_access'
    }
}

I can manually curl to get the tokens like described here

I would appreciate any pointers.

@adamjmcgrath
Copy link
Contributor

This looks like it's been resolved by https://github.com/panva/node-oidc-provider/issues/697#issuecomment-612436061

Feel free to reopen if not

@MatthiasGrandl
Copy link
Author

I solved this issue by writing my own client. Not sure why I am the only one who encounters this issue, perhaps some other middleware causes issues. It's ok if this remains closed for now.

@panva
Copy link
Contributor

panva commented May 17, 2020

Fixed by #86

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants