Best Practice with Client Credentials with refresh token and id token.

[foresx]

Describe the solution you'd like

I want to configure user info in hydra client. So that I can get access token and use access token to ask userinfo endpoint to get the user info. In this way, I can use the same logic to deal with all access token.

And I see oauth2.0 and hydra's client credentials flow without refresh token, So what is the best practice?
Should I use client id and client secret to ask access token each time? Or I maintain a access token's cache and update it.

And also, for more learning. Can you plz tell me what's your thinking about client credentials without id token and refresh token.
What's the advantage of it?

I use hydra in our company production environment, and it works well. I love it, and thanks to all contributers.

[foresx]

I see you closed the issue and move it into discussions, sry. @aeneasr

[foresx]

Look forward to your feedback...

[vinckr]

Hey, sorry for the late reply, its been busy.
I think so far we do not have a lot of documentation on this. I guess it is up to you which method you use.
In the quickstart we use client id and secret. Is it a problem to use this each time?
I can't give you solid advice, but I would love to find out. Maybe we could even add to the documenation a bit, there is not a lot regarding client credentials flow there.

[vinckr]

Hey @foresx Just checking in if you are still stuck on this issue or if I can help you further in any way.

[vinckr]

This topic seems to be stale, so closing it for now.

[foresx]

sorry for the late response cause of the Chinese Spring Festival. I learn something from keycloak. Client Credentials can not have a refresh token or ID token in the future in keycloak too. So how to do if we want to control client's authz so that we can use it like a normal user? Is there some good practice in hrydra.

[vinckr]

Dont worry about it!
What do you mean by "use it like a normal user"?