The IrregularChat Login: Difference between revisions

Line 6:

Issues with previous identity solutions:

* **Local Login**: One login per account is inconvenient and less secure, especially when users don’t always have access to a password manager. Local logins also present more vulnerabilities and require constant patching. As our community grows, this solution is not sustainable.

* '''Local Login''': One login per account is inconvenient and less secure, especially when users don’t always have access to a password manager. Local logins also present more vulnerabilities and require constant patching. As our community grows, this solution is not sustainable.

* **GitHub**: Surprisingly, only a small portion of our members had GitHub accounts. While we attempted to use it as a forcing function, it became a barrier for simpler services like a wiki. GitHub also lacks automation and control for logins unless you opt for an expensive enterprise account.

* '''GitHub''': Surprisingly, only a small portion of our members had GitHub accounts. While we attempted to use it as a forcing function, it became a barrier for simpler services like a wiki. GitHub also lacks automation and control for logins unless you opt for an expensive enterprise account.

* **KeyCloak**: Another self-hosted solution, but not as intuitive for managing the variety of services within our community.

* '''KeyCloak''': Another self-hosted solution, but not as intuitive for managing the variety of services within our community.

* **Google**: While secure, Google raises privacy concerns, and depending on a large corporation for identity management wasn’t ideal for our self-hosted philosophy.

* '''Google''': While secure, Google raises privacy concerns, and depending on a large corporation for identity management wasn’t ideal for our self-hosted philosophy.

== Common Issues and Questions ==

@@ Line 6: / Line 6: @@
 Issues with previous identity solutions:
-* **Local Login**: One login per account is inconvenient and less secure, especially when users don’t always have access to a password manager. Local logins also present more vulnerabilities and require constant patching. As our community grows, this solution is not sustainable.
+* '''Local Login''': One login per account is inconvenient and less secure, especially when users don’t always have access to a password manager. Local logins also present more vulnerabilities and require constant patching. As our community grows, this solution is not sustainable.
-* **GitHub**: Surprisingly, only a small portion of our members had GitHub accounts. While we attempted to use it as a forcing function, it became a barrier for simpler services like a wiki. GitHub also lacks automation and control for logins unless you opt for an expensive enterprise account.
+* '''GitHub''': Surprisingly, only a small portion of our members had GitHub accounts. While we attempted to use it as a forcing function, it became a barrier for simpler services like a wiki. GitHub also lacks automation and control for logins unless you opt for an expensive enterprise account.
-* **KeyCloak**: Another self-hosted solution, but not as intuitive for managing the variety of services within our community.
+* '''KeyCloak''': Another self-hosted solution, but not as intuitive for managing the variety of services within our community.
-* **Google**: While secure, Google raises privacy concerns, and depending on a large corporation for identity management wasn’t ideal for our self-hosted philosophy.
+* '''Google''': While secure, Google raises privacy concerns, and depending on a large corporation for identity management wasn’t ideal for our self-hosted philosophy.
 == Common Issues and Questions ==