-
Notifications
You must be signed in to change notification settings - Fork 33
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
Make the bearer-strategy mandatory #209
Labels
Comments
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 12, 2024
make bearer strategy non optional, resulting client password strategy also not optional GH-209
12 tasks
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 12, 2024
make bearer stratgegy mandatory, which needs client password strategy GH-209
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 12, 2024
make client password strategy mandatory as it needs to be for any authentication by any strategy. Also, make bearer stratgey mandatory as everybody use it GH-209
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 15, 2024
make client password strategy mandatory as it needs to be for any authentication by any strategy. Also, make bearer stratgey mandatory as everybody use it GH-209
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 15, 2024
make client password strategy mandatory as it needs to be for any authentication by any strategy. Also, make bearer stratgey mandatory as everybody use it GH-209
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 15, 2024
make client password strategy mandatory as it needs to be for any authentication by any strategy. Also, make bearer stratgey mandatory as everybody use it GH-209
🎉 This issue has been resolved in version 11.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Make the bearer-strategy mandatory
Keep the others non-mandatory
The text was updated successfully, but these errors were encountered: