Added the possibility to use multiple or other authentication methods

[IncredibleRichie]

No description provided.

[stale]

This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark pull requests as stale.

[IncredibleRichie]

This would like it to make it in the code :-)

[stale]

This issue is no longer marked for closure.

[github-actions]

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[IncredibleRichie]

This would like it to make it in the code :-)

[github-actions]

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[IncredibleRichie]

This would like it to make it in the code :-)

[github-actions]

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[eternaltyro]

@geerlingguy I know you are busy, can you update the stale bot to close stale PR after 3-months or so?

[geerlingguy]

I set it to auto-close if there's no response for X amount of time after the 'stale' message is posted, and I think X is 90 days. Usually if I don't get to an issue right away (and with hundreds of projects, that's most of the time), it's not affecting me personally and there's a good chance it won't make it in.

This particular feature request is something I don't use personally (I don't ever use password auth), but I see there could be some value. I don't think we need the added complexity of automatic identification of whether password auth should be set to 'yes' or 'no' though. It would be a simpler PR to review/maintain if it just added the new var and kept the existing one set to 'no'.