Auth method should an explicit option
See original GitHub issueCurrently the auth method used is determined by which of the first in an array of methods happens to be enabled. This is not very intuitive to configure for users and will only get worse as more auth methods are added. This should be an explicit option, for example:
//
// Set the authentication.
// Options include "local" and "ldap"
//
// @type string
// @default "local"
//
auth: "local",
If the chosen auth method is disabled internally because of incomplete configuration then throw and error at startup.
I ran into this when I was working on creating my own auth method. Making it work to begin with was confusing. I’m willing to make the changes, I just want to see if I should take the effort.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Documentation: 10: 20.3. Authentication Methods - PostgreSQL
When trust authentication is specified, PostgreSQL assumes that anyone who can connect to the server is authorized to access the database with whatever ......
Read more >User authentication | StoreFront 1912 LTSR
Users enter their credentials and are authenticated when they access their stores. Explicit authentication is enabled by default. All user ...
Read more >Policies | Vault - HashiCorp Developer
Default Policy By default, it is attached to all tokens, but may be explicitly excluded at token creation time by supporting authentication methods....
Read more >Explicit proxy authentication - Fortinet Documentation Library
Explicit proxy authentication is managed by authentication schemes and rules. An authentication scheme must be created first, and then the authentication rule.
Read more >Web Authentication Methods Explained - Blog - RisingStack
HTTP authentication methods · the username and password are sent with every request, potentially exposing them – even if sent via a secure ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’d like to add SAML2 authentication support to The Lounge. It sounds like this is a good opportunity to make auth methods more properly pluggable. I’m willing to take a look at this.
@YaManicKill I think it’s easier to just remove
private/public
definition in favor ofauth
, so you’d setauth: public
(or none) to disable auth.