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

Usage of "public clients" / "deployments traditionally viewed as a public client" #79

Open
paulbastian opened this issue May 22, 2024 · 3 comments
Labels

Comments

@paulbastian
Copy link
Collaborator

          "public clients" ... "to authenticate" is a contradiction. The text further up speaks about "deployments traditionally viewed as a public client", that's a better description. I would even argue either this spec is for confidential clients of a new kind or it is a new type of client. But it is not for public clients.

Originally posted by @tlodderstedt in #74 (comment)

@paulbastian
Copy link
Collaborator Author

What would be the downside of defining a new type of client, e.g. attested client?

@jogu
Copy link

jogu commented Sep 11, 2024

It sounds similar to 'credentialed client', a concept that OAuth 2.1 toyed with and ultimately decided didn't help: oauth-wg/oauth-v2-1#107

@babisRoutis
Copy link

What would be the downside of defining a new type of client, e.g. attested client?

I am not sure about the spec, yet Attested Client was the term to use in our VCI library.

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

No branches or pull requests

3 participants