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

Question: about the design of ClientInfo interface #758

Open
yangtuooc opened this issue Nov 28, 2024 · 0 comments
Open

Question: about the design of ClientInfo interface #758

yangtuooc opened this issue Nov 28, 2024 · 0 comments

Comments

@yangtuooc
Copy link

I have a question about the design of the ClientInfo interface, specifically about the GetUserID() method:

type ClientInfo interface {
GetID() string
GetSecret() string
GetDomain() string
IsPublic() bool
GetUserID() string // <-- This method
}

According to OAuth2 specification, a Client typically represents a third-party application. However, the GetUserID() method in the interface seems to suggest a one-to-one relationship between a Client and a User.

Questions:

  1. What's the intended use case for GetUserID()?
  2. How should this be used in scenarios where one Client serves multiple users?

I'm trying to understand the design rationale to better implement this interface in my application.

@yangtuooc yangtuooc changed the title Question about the design of ClientInfo interface Question: about the design of ClientInfo interface Nov 28, 2024
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

1 participant