AppFlowy-IO/AppFlowy

Fork 0

mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 12:56:59 +00:00

[GH-ISSUE #4756] [FR] Self-host more sign-up/login options #2128

New issue

Closed

opened 2026-03-23 21:19:52 +00:00 by mirror · 14 comments

mirror commented

2026-03-23 21:19:52 +00:00

Owner

Originally created by @yujinio on GitHub (Feb 27, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4756

Description

AppFlowy is advertised as a privacy-first service, but for some reason only allows to sign-up and login through the most anti-private third-party oauth vendors available: github (microsoft), discord and google.

I'd suggest to implement a few more options to sign-up and login.

And no, using the app in offline mode only is not a solution to the problem I'm highlighting IMO.

Impact

By adding other OAuth2 providers:

More users (audience growth);
More privacy (with privacy-friendly vendors).

By adding other sign-up/login options:

Flexibility;
More privacy.

Additional Context

I couldn't find if such an issue already exists, so sorry in advance if I'm duplicating it.

Originally created by @yujinio on GitHub (Feb 27, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4756 ### Description AppFlowy is advertised as a privacy-first service, but for some reason only allows to sign-up and login through the most anti-private third-party oauth vendors available: github (microsoft), discord and google. I'd suggest to implement a few more options to sign-up and login. And no, using the app in offline mode only is not a solution to the problem I'm highlighting IMO. ### Impact By adding other OAuth2 providers: - More users (audience growth); - More privacy (with privacy-friendly vendors). By adding other sign-up/login options: - Flexibility; - More privacy. ### Additional Context - _I couldn't find if such an issue already exists, so sorry in advance if I'm duplicating it._

mirror

2026-03-23 21:19:52 +00:00

closed this issue
added the
self-hosted

login
labels

mirror commented

2026-03-23 21:19:53 +00:00

Author

Owner

@moolight-seashell commented on GitHub (Mar 28, 2024):

this should be high priority in the things to do

@moolight-seashell commented on GitHub (Mar 28, 2024): this should be high priority in the things to do

mirror commented

2026-03-23 21:19:53 +00:00

Author

Owner

@annieappflowy commented on GitHub (Mar 29, 2024):

We've enabled the backend to support sign in with magic link or password and will work on the frontend in April
What other OAuth2 options would you like to use?

@annieappflowy commented on GitHub (Mar 29, 2024): We've enabled the backend to support sign in with magic link or password and will work on the frontend in April What other OAuth2 options would you like to use?

mirror commented

2026-03-23 21:19:54 +00:00

Author

Owner

@moolight-seashell commented on GitHub (Mar 29, 2024):

first be able to connect with password and magic links on pc and android,

then
maybe use 2 factors authentification with one time password like do Aegis. or even all FIDO like devices like yubikey.
Probably hard to implement if superbase d'ont support them but well this app pretend to be a secure note app, right ? =P =)

Personnaly i d'ont see why you're using these these third-party OAuth2 at all and even with google mircosoft or others

@moolight-seashell commented on GitHub (Mar 29, 2024): first be able to connect with password and magic links on pc and android, then maybe use 2 factors authentification with one time password like do Aegis. or even all FIDO like devices like yubikey. Probably hard to implement if superbase d'ont support them but well this app pretend to be a secure note app, right ? =P =) Personnaly i d'ont see why you're using these these third-party OAuth2 at all and even with google mircosoft or others

mirror commented

2026-03-23 21:19:54 +00:00

Author

Owner

@yujinio commented on GitHub (Mar 30, 2024):

@annieappflowy

We've enabled the backend to support sign in with magic link or password and will work on the frontend in April

Hi Annie,

These are some great news, thanks!
Looking forward to seeing an option to sign in with magic link or password in desktop and mobile apps.

What other OAuth2 options would you like to use?

For those who self-host it might be convenient to have an option to implement a custom OIDC OAuth2 provider support, e.g. Keycloak, Authelia, etc. Some open-source services (e.g. Gitea/Forgejo, Outline) support OIDC.

Speaking about publicly available OAuth2 providers, I'm not sure. I personally wouldn't use any because I prefer not to rely on any third-party (MITM) to access any kind of a service.

P.S. here's a wiki list of OAuth2 providers if you need it: https://en.wikipedia.org/wiki/List_of_OAuth_providers

@yujinio commented on GitHub (Mar 30, 2024): @annieappflowy > We've enabled the backend to support sign in with magic link or password and will work on the frontend in April Hi Annie, These are some great news, thanks! Looking forward to seeing an option to sign in with magic link or password in desktop and mobile apps. > What other OAuth2 options would you like to use? For those who self-host it might be convenient to have an option to implement a custom OIDC OAuth2 provider support, e.g. Keycloak, Authelia, etc. Some open-source services (e.g. Gitea/Forgejo, Outline) support OIDC. Speaking about publicly available OAuth2 providers, I'm not sure. I personally wouldn't use any because I prefer not to rely on any third-party (MITM) to access any kind of a service. P.S. here's a wiki list of OAuth2 providers if you need it: https://en.wikipedia.org/wiki/List_of_OAuth_providers

mirror commented

2026-03-23 21:19:54 +00:00

Author

Owner

@flavienbwk commented on GitHub (Aug 7, 2024):

Is there any current work allowing AppFlowy to be used with SSO such as Keycloak ? (OIDC)

@flavienbwk commented on GitHub (Aug 7, 2024): Is there any current work allowing AppFlowy to be used with SSO such as Keycloak ? (OIDC)

mirror commented

2026-03-23 21:19:54 +00:00

Author

Owner

@jernejcvek commented on GitHub (Oct 30, 2024):

Is there any current work allowing AppFlowy to be used with SSO such as Keycloak ? (OIDC)

That would be awesome since Keycloak is open source and, besides integrated auth, provides the possibility to use other identity providers as well.

@jernejcvek commented on GitHub (Oct 30, 2024): > Is there any current work allowing AppFlowy to be used with SSO such as Keycloak ? (OIDC) That would be awesome since Keycloak is open source and, besides integrated auth, provides the possibility to use other identity providers as well.

mirror commented

2026-03-23 21:19:54 +00:00

Author

Owner

@yggi commented on GitHub (Nov 15, 2024):

👍 Just found this when researching how to authenticate to appflowy with a different oauth provider. Would ❤️ to have it playing nice with authelia

@yggi commented on GitHub (Nov 15, 2024): :+1: Just found this when researching how to authenticate to appflowy with a different oauth provider. Would :heart: to have it playing nice with authelia

mirror commented

2026-03-23 21:19:55 +00:00

Author

Owner

@JorySeverijnse commented on GitHub (Jan 12, 2025):

Any update with providing more login options, would really love to see this so i could switch over to appflowy :)

@JorySeverijnse commented on GitHub (Jan 12, 2025): Any update with providing more login options, would really love to see this so i could switch over to appflowy :)

mirror commented

2026-03-23 21:19:55 +00:00

Author

Owner

@khorshuheng commented on GitHub (Jan 13, 2025):

If you need support for Authelia, Okta etc, currently, it should be possible to use SAML 2.0.

@khorshuheng commented on GitHub (Jan 13, 2025): If you need support for Authelia, Okta etc, currently, it should be possible to use SAML 2.0.

mirror commented

2026-03-23 21:19:55 +00:00

Author

Owner

@almereyda commented on GitHub (Feb 8, 2025):

Most of the gotrue supported providers are working. I'm successfully logging in to the admin /console with GitLab, for example.

Therefore this seems to be superseded by:

#6834

@almereyda commented on GitHub (Feb 8, 2025): Most of the gotrue supported providers are working. I'm successfully logging in to the admin /console with GitLab, for example. Therefore this seems to be superseded by: - #6834

mirror commented

2026-03-23 21:19:55 +00:00

Author

Owner

@khorshuheng commented on GitHub (Feb 9, 2025):

@almereyda How did you login via gitlab? While gotrue does support this, I can't think of a way to login via gitlab unless the admin console / AppFlowy Web login page has been modified to add gitlab as an option.

@khorshuheng commented on GitHub (Feb 9, 2025): @almereyda How did you login via gitlab? While gotrue does support this, I can't think of a way to login via gitlab unless the admin console / AppFlowy Web login page has been modified to add gitlab as an option.

mirror commented

2026-03-23 21:19:55 +00:00

Author

Owner

@almereyda commented on GitHub (Feb 9, 2025):

The admin console was recently extended.

It was in

https://github.com/AppFlowy-IO/AppFlowy-Cloud/pull/874

@almereyda commented on GitHub (Feb 9, 2025): The admin console was recently extended. It was in - https://github.com/AppFlowy-IO/AppFlowy-Cloud/pull/874

mirror commented

2026-03-23 21:19:56 +00:00

Author

Owner

@annieappflowy commented on GitHub (Apr 18, 2025):

We recently supported:

login with OTP
paste the magic link into the browser to redirect

We'll soon support login with password.

@annieappflowy commented on GitHub (Apr 18, 2025): We recently supported: 1. login with OTP 2. paste the magic link into the browser to redirect We'll soon support login with password.

mirror commented

2026-03-23 21:19:56 +00:00

Author

Owner

@tz-torchai commented on GitHub (Dec 25, 2025):

Let me know if this should be a separate issue, but I think it’s related.

We should support OIDC (OAuth 2.0) sign-in in addition to SAML 2.0. OIDC is the recommended and more modern approach compared to SAML.

There are too many social login providers to support individually, so AppFlowy shouldn’t try to integrate each one directly. OIDC support solves this problem in a scalable way.

@tz-torchai commented on GitHub (Dec 25, 2025): Let me know if this should be a separate issue, but I think it’s related. We should support OIDC (OAuth 2.0) sign-in in addition to SAML 2.0. OIDC is the recommended and more modern approach compared to SAML. There are too many social login providers to support individually, so AppFlowy shouldn’t try to integrate each one directly. OIDC support solves this problem in a scalable way.

mirror referenced this issue

2026-03-23 22:17:17 +00:00

[PR #2128] [CLOSED] release 0.1.2 #5111