On my site (https://discuss.openedx.org), I don’t see Associated Accounts when I go to edit my profile, like I do when I edit my profile here. But I can’t see anything in settings or plugins that looks like something I have to enable. What am I missing?

It’s suppressed when 2FA is enabled.

Maybe the problem here is I’m misunderstanding what they are for. I wanted a way for people to add their Twitter and GitHub accounts so that other users could see them. For example, to follow people they meet in the forum. But it’s becoming clearer that the fields I see in my profile here are really only for authentication, and so are not displayed to others. In fact, in the admin panels, they are treated with the same secrecy as email address, with an explicit button to view. If I want publicly visible Twitter and GitHub handles, do I have to add them as custom user fields myself?

Traditionally that is done in the About Me field as free text, so yes.

Although a necro bump, this is super relevant and at the top of Google right now: Is there a 2020 solution for this? Currently, existing forum users that donate via Patreon are locked out from any Discourse rewards. This is a pretty big problem since 2FA is super important and growing in popularity (as it should). We don’t want users to essentially be punished for adding 2FA~ Can’t we just get users to confirm 2fa before connecting any link? It seems outlandish to just remove this feature completely. I have 2FA enabled on Discord, too, for example – should I not be able to connect any account after that?

The Patreon plugin doesn’t need the social login for it to work. As long as the email match, local logins will work just as fine and the emails will be assigned to their correct groups.

Ohhhh… can we add that to Patreon OP? That’s pretty important. I couldn’t figure out why this guy couldn’t get linked and didn’t know where to turn. This may help others~ However, associated account linking is still pretty nice - some would even say necessary. I’m sure not everyone uses the same email for everything (I don’t) for different reasons. Some may also use aliases (eg, me+someAlias@gmail.com): Can we get associated account linking even when someone 2FA’s up? Feels like a pretty big downgrade considering how important 2FA is; not the most encouraging to enable it if you lose features.

[image] dylanh724: However, associated account linking is still pretty nice - some would even say necessary. I’m sure not everyone uses the same email for everything (I don’t) for different reasons. Some may also use aliases (eg, me+someAlias@gmail.com): @dylanh724, that’s my situation. I don’t merely utilise RFC 5233 sub-addresses, but different local parts (albeit, with the same subdomain) per service: https://github.com/nextcloud/contacts/issues/3530#issue-1816825315 Others utilise different local parts and a generic domain that doesn’t relate to them, for which this cannot even theoretically be supported any other way. Consequently, I want to explain that the undermentioned is nonsensical: [image]Why is 2FA incompatible with Associated Accounts? [image]Why is 2FA incompatible with Associated Accounts? It seems 2FA is mutually exclusive with associated accounts: [image] Falco: It’s suppressed when 2FA is enabled. Why is this? […] the reason being is that your associated accounts can also be compromised, and AFAIK associated accounts bypass the 2FA restriction on forum accounts. That is why 2FA suppresses associated accounts. Associated accounts can be compromised, especially without 2FA allowing bad-actors to therefore, log into your forum account as well. I’ve 2FA enabled. Currently, via TOTP, but shall be via CTAP1, when the undermentioned has been resolved: [image] Allow storing multiple passkeys on one vault item Feature Requests Password Manager app:all server:default-cloud Use case: As a user of a website with multiple Top Level Domains (TLD), I want to be able to store multiple passkeys for one Vault Entry. Reason: Passkeys are made so that they are usable only for one relying party ID to avoid phishing attacks... Reading time: 16 mins 🕑 Likes: 34 ❤ This is solely for username-plus-password entry. Instead, I’ve also CTAP2 1FA active for the account. It’s also active for all possible OAuth alternatives, thereby rendering the stated rationale for preventing connecting alternative SSO options quite outdated. It’s also quite confusing for someone who isn’t aware of the restriction: [image] Shall KDE Bugzilla and/or Discourse ever be connected to Identity or GitLab SSO? Brainstorm discourse bugs I guess Bugzilla is just too old or otherwise cumbersome to do this. However discuss.kde.org can do this already. The option is called “as a KDE Contributor”. Consequently, I advise that this not be the default, especially whilst the undermentioned remains: [image] Passkey option missing on "Enforce second factor on external auth" error screen Bug With enforce_second_factor_on_external_auth enabled, if a user attempts to log in via social auth they get to this screen: [image] But the option to log in via passkey is missing. It should be added to this screen. That, plus the general dissuasion toward 2FA, means that it’s a net security negative.

How do I enable Associated Accounts with 2FA?

Product Support

Falco (Falco) September 29, 2019, 3:20am 6

You can try (Retired) Use an ID in a custom user field to link to a user's external profile - #2 by techAPJ if that is what you need.

Topic		Replies	Views
How do existing Discourse end-users link Patreon? Product Support patreon	7	1945	April 13, 2020
Why is 2FA incompatible with Associated Accounts? Product Support 2fa	1	209	March 10, 2025
Associated Accounts disabled when secondFactor is enabled Product Support	0	420	April 30, 2022
Is it impossible to remove Associated Accounts? Product Support	12	1002	April 14, 2022
Associated Accounts are not visible on staff accounts? Product Support	4	158	March 23, 2026

How do I enable Associated Accounts with 2FA?

Related topics