You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating many different authn strategies is an anti-pattern to be avoided. Ideally, applications either only use capabilities (e.g., zcaps / some form of OAuth2) or they use simple authn (multifactor) to establish sessions that can then be used to invoke capabilities or use access tokens via OAuth2.
Therefore, this module should simplified to only support session-based authn (and see #53 for CSRF-protections). Support is still required for the strategies (tokens + multifactor) used in bedrock-authn-token-http, so simplification should consider this. Perhaps this module should even just be merged with bedrock-authn-token-http.
The text was updated successfully, but these errors were encountered:
Creating many different authn strategies is an anti-pattern to be avoided. Ideally, applications either only use capabilities (e.g., zcaps / some form of OAuth2) or they use simple authn (multifactor) to establish sessions that can then be used to invoke capabilities or use access tokens via OAuth2.
Therefore, this module should simplified to only support session-based authn (and see #53 for CSRF-protections). Support is still required for the strategies (tokens + multifactor) used in bedrock-authn-token-http, so simplification should consider this. Perhaps this module should even just be merged with
bedrock-authn-token-http
.The text was updated successfully, but these errors were encountered: