Obviously I’m testing with several accounts I created just for this purpose (using virtual machines and other browsers and too much time testing 
).
I think I resolved the issue on my end. It had nothing to do with Discourse.
There’s a bit of code in my site’s footer that checks – for users whose email has been verified – if they are logged in to Discourse already and, if they aren’t, logs them in. This informs Discourse of users’ info, even if they don’t visit the forum itself.
Alas, this chunk was being accidentally cached so, of course, it wasn’t firing because it had been cached when no user had logged in. My bad! 
3 Mi Piace
This is probably the best place still to mention that there are cases when Discourse drives me absolutely nuts.
I happen to have several “users” that are not real. Whether they are read-only accounts for a specific hidden category, anonymous beyond the capabilities of Discourse or whatever should not matter. Some of these are automatic and created on the fly as needed (and reused in a queue).
Problem is, they have been added using a “noreply” email. That email does not exist anymore so Discourse is spamming out admin mails saying this email bounced, all the time, for each of these users and the moderators are now starting to go nuts.
Now, if I go in and change that email to an existing no-forward, no-store email, Discourse refuses to do it without sending a mail to said email asking for confirmation… so no changes are made. Anyone see the problem here? 
So I have two options I can think of:
Log in as each user using SSO to force an email change (which hopefully does not require confirmation, haven’t actually tried, would be too tedious).
Go to the preferences of each such user and change email notifications and summary digests to never, ever. And every time a new temporary user gets created, I need to remember to do the same.
Maaaaan. If I as an admin change an email for a user, there is no need to ask the user to confirm the email. Any user will hopefully contact me if I actually messed up which is very unlikely. Besides, these days I just let the users change their emails at will, less trouble for a poor admin. And I understand there is a risk that the user will never be able to login or notify anyone again but obviously they can mail the site help as such.
1 Mi Piace
Why not use the sync_sso endpoint to fix all the emails via api?
2 Mi Piace
Not sure what you mean by this. Are you talking about the setting “sso overrides email”?
That would only take effect when/if the user actually logs in. So emails would still bounce while the email is wrong.
If you are possibly talking about “POST admin endpoint /admin/users/sync_sso to synchronize an SSO record” that would mean I would have to force one or all users from the SSO software I guess. Given the problems with SSO emails syncing it’s not the first option I would try.
Anyway, because of the problem described earlier in this topic I now have “sso overrides email” off and let users change their emails themselves. So I don’t want to override from SSO anymore.
But all this is missing the point, that the users bouncing mails are generated on the fly, as needed. The easiest way would be to allow a change to the email without authentication (at least for admins - or admins would have a choice).
Side note: I have tried giving an empty email address but the system does not allow for that. I understand the email address is so critical is should not be empty. BUT, if you really give an empty email (at least as an admin), one could assume you know what you are doing.
Just to confuse things more, I actually have users that do not have an email account, only access to a browser. Think refugees here and you might understand why. It is far easier to just allow someone to login and read instructions in their own language than to try and explain to them they need to make a gmail account or something.
In any case, this is theoretical, I doubt many people have the same problem. I would say it’s simply too strict even for admins, IMHO.
(sorry about the reply time, with more free time the world would be perfect)
1 Mi Piace
That would allow someone to hijack an admin’s account without their knowing. Though your edge case for users without access to email makes some sense, it seems far-fetched to think that admins would be people who don’t have the ability to receive email.
2 Mi Piace
Admins have email addresses. Not sure where you got the idea they would not have (my bad writing probably ).
The case was for an admin to be able to change other user’s emails without the need to authenticate.
1 Mi Piace
So I’m trying to do this - the use case is a user has changed their email in the SSO system, however they now can’t log in since there’s another account of theirs that uses their new email address already. SSO refuses to update the email (even though we have sso_overrides_email on) because email addresses must be unique across accounts. I don’t want to delete the account without the SSO record as that has posts associated with it. And if I turn off sso_overrides_email to change the email manually, I can’t make it some broken email since Discourse insists on validating it.
I see there’s a way to merge users but a) it’s a rake task and we’re hosted with Discourse, do I contact support to do that? b) there’s comments about needing to swap the primary and secondary email addresses.
1 Mi Piace
I’m in the same boat @trs80. Did you ever find out if there is a way to workaround this limitation of the merging?
I’ll have to check my email but support have generally been pretty good with resolving these issues.
2 Mi Piace
“impostalo per sovrascrivere le email”
È questa l’impostazione “auth overrides email”?
1 Mi Piace
Non male AI, felice di questa risposta:
AI explainer on auth overrides emails AI
sam:
cosa fa l’email di override dell’autenticazione?
gpt4_bot:
Leggi le impostazioni del sito
Lettura del contesto per: auth_overrides_email
- Sovrascrive l’indirizzo email locale con l’indirizzo email fornito dal provider di autenticazione esterno (ad esempio, SSO, OAuth) ad ogni accesso dell’utente.
- Impedisce all’utente di apportare modifiche locali al proprio indirizzo email nelle impostazioni dell’account Discourse.
Questa funzionalità è applicabile a tutti i provider di autenticazione configurati sul sito Discourse. Questa impostazione è utile quando si desidera mantenere la coerenza delle email e la verifica dell’identità per gli utenti che accedono tramite servizi esterni.
Tuttavia, gli utenti dovrebbero prestare attenzione con questa impostazione, poiché possono verificarsi discrepanze a causa della normalizzazione degli indirizzi email locali. Ciò significa che se vi è una differenza nel modo in cui il sistema esterno e Discourse formattano o gestiscono gli indirizzi email, ciò potrebbe portare a corrispondenze errate o problemi con il collegamento dell’account.
Il valore predefinito per auth_overrides_email è false, il che significa che, per impostazione predefinita, Discourse non sovrascrive le email locali con le email del sito esterno ad ogni accesso, né impedisce agli utenti di modificare i propri indirizzi email.
Quando questa impostazione è abilitata, influisce su varie autorizzazioni dell’utente, inclusa l’impossibilità di modificare gli indirizzi email in determinati casi, come gestito dagli script guardian del sito e guardian dell’utente. Inoltre, l’impostazione influisce su come vengono visualizzati i campi email e se agli utenti vengono fornite istruzioni relative alle modifiche dell’indirizzo email all’interno dell’interfaccia utente.
1 Mi Piace
Ho anche problemi qui. Discourse ottiene le sue informazioni SSO dal mio sito WordPress e auth_overrides_email è abilitato.
Tuttavia, quando aggiorno l’indirizzo email dell’utente in WordPress, non vengono apportate modifiche su Discourse.
Ho provato a disattivare auth_overrides_email e, sebbene ciò abbia rimosso il commento che indicava che era gestito da un provider di autenticazione, non è mai apparsa un’icona a forma di matita accanto all’indirizzo email, né per me come amministratore né quando impersonavo l’utente (cosa che ho fatto diverse volte prima di disattivare l’impostazione per simulare il login/logout suggerito sopra). Tutto ciò che potevo fare era mostrare l’indirizzo.
Ho riattivato auth_overrides_email e ho modificato l’indirizzo altre due volte in WordPress (prima a qualcos’altro e poi di nuovo a quello che dovrebbe essere), senza alcun cambiamento.
Suggerimenti?
Ho lo stesso problema. C’è un modo per cambiare l’email dell’utente nel database di Discourse? Come posso farlo dalla riga di comando?
1 Mi Piace
Di solito devo abilitare emails_editable, quindi disabilitare auth_overrides_email, quindi modificare l’email.
1 Mi Piace
Se li costringi a disconnettersi in modo che debbano accedere di nuovo, l’indirizzo email viene passato a Discourse?
1 Mi Piace