Authentication by third parties on registration & login

[networkimprov]

A publicly accessible mnm site needs ways to identify & authenticate people registering new accounts. Possibilities include:

• HumanID https://human-id.org
• Twitter (etc) verified accounts
• Designated OpenID Connect providers

A private mnm site needs ways to limit registrations & (often) logins to specific people or groups. Possibilities:

• LDAP
• Kerberos

A mnm site shall be able to require authentication on registration & login, or only registration. Private sites would typically require both; public sites would not (as that means a third-party action can deny someone access to email).

[networkimprov]

The initial OpenID Connect implementation is in 4aa2b88a.

See docs under https://github.com/networkimprov/mnm#configuration.

[ghost]

Hi networkimprov.

A mnm site shall be able to require authentication on registration & login, or only registration. Private sites would typically require both; public sites would not (as that means a third-party action can deny someone access to email).

Would it be possible to use oauth for authentication in tmtp?

[networkimprov]

Please see commit mentioned above re OpenID Connect, which is oauth2 based.

[ghost]

Hi networkimprov.

Please see commit mentioned above re OpenID Connect, which is oauth2 based.

thank you for feedback here.