-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
resource_owner always required for Plug.VerifyHeader #40
Comments
Yeah, the |
Added a quick PR that you can try out. I haven't dug into the specification to be sure that this is how it should work, but this might be what you need to continue your work. |
Works, exactly what I needed to continue. Thanks for the quick response & PR! |
v0.4.3 is out! |
I'm trying use an application-wide bearer token (not bound to any user) to use for metadata endpoints and third party application connections.
I created a new OauthApplication with a client_id and client_secret (and set the resource_owner to the user that creates the application in the backend).
I can retrieve an access_token from the token endpoint using the client_credentials grant but I am unauthorized when going to an API endpoint. It appears resource_owner is explicitly set to
nil
in the client_credentials.grant flow:The VerifyHeader plug then returns
{:no_association_found}
when resource_owner isnil
Is this intended or a bug?
The text was updated successfully, but these errors were encountered: