'None' authentication method for authorization code flow with PKCE?
Open
enhancement
- Dominant language
- Erlang
- Stars
- 240
- Forks
- 69
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 4
Description
### Description
According to the docs, there are four supported authentication methods: `client_secret_basic`, `client_secret_post`, `client_secret_jwt`, and `private_key_jwt`.
As such, all functions in `Oidcc` require both a client ID and client secret, such as: https://hexdocs.pm/oidcc/Oidcc.Token.html#retrieve/3
Is it possible to support not providing a client secret so that the client can still fetch and exchange access tokens?
Contributor guide
Assessment
This issue has not been assessed yet.