#772 support for stacked authentication providers

Reporter Dan
Owner Nobody
Stars ★★ (2)
  • Status-New
  • Priority-Medium
  • Type-Enhancement
  1. Dan on

    Please add the possibility to stack several authentication providers.

  2. Zash on

    Hi. Is there a specific reason you are requesting this? This has been discussed before. It's not hard to combine two authentication modules, but doing it in a generic way is tricky, especially when hashed authentication mechanisms are involved.

  3. Dan on

    Hi, yes, I would like to have one authentication provider to be tried first (e.g. LDAP) and if the authentication there fails, to try the credentials with another provider (e.g. mod_auth_external).

  4. Kris on

    Would be nice to have in the following scenario: Do the main authentication against an external provider (for example Nextcloud JSXC), but have Prosody only accounts for admin functionality and running a bot like errbot. Currently I would need an non-functional errbot account in Nextcloud to allow it to connect to Prosody. With stacked authentication I could have them in the internal user storage along side the Nextcloud accounts. Another similar scenario would be different front-ends, such as running a public chat service and a XMPP enabled Nextcloud instance, with interoperability, but not wanting to create a Nextcloud account for every common chat user. Thanks a lot for looking into this!

  5. Yegor on

    How in 2024 we can use stack several authentication providers? I need to use jwt and wordpress (mysql) authentication providers at same time.

New comment

Not published. Used for spam prevention and optional update notifications.