stale-leather-91675
05/16/2022, 3:20 PM--token-endpoint-auth-method none
but also have the gran-type: client_credentials
.
Currently when you create a new client with --token-endpoint-auth-method none
you don’t get a client-secret
.
I guess this might be something you don’t want to do?proud-plumber-24205
05/17/2022, 8:09 AMstale-leather-91675
05/17/2022, 8:21 AMclient_credentials
. I’m not interested in this case to make request on the behalf of a user but instead use access the applications own resources.stale-leather-91675
05/17/2022, 8:38 AMauthorization_code
flow to let the app make request on the behalf of a user but still use the client_credentials
to let the application itself make non user request to update some common resources.
https://www.oauth.com/oauth2-servers/access-tokens/client-credentials/
and not
https://www.oauth.com/oauth2-servers/access-tokens/password-grant/proud-plumber-24205
05/17/2022, 9:13 AMproud-plumber-24205
05/17/2022, 9:15 AMstale-leather-91675
05/17/2022, 9:44 AMauthorization_code
with PKCE without a secret but also use some M2M auth on the backend using client_credentials
.
As you mentions it works fine when you can use a confidential client and use both id and secret but for the public case no secret is generated when creating a client making it so you are missing information go trough with the client_credentials
flow.stale-leather-91675
05/17/2022, 10:39 AM