2023-09-02T01:45:51 luc14n0, re-assigned that poo# to acidsys as normal priority ;) 2023-09-02T01:58:08 luc14n0, there have been a number of tickets created by the user, they missed all the previous (many years) opportunities availed to fix this, with the move to Discourse and IDP, those that haven't are prettym much SOL 2023-09-02T02:19:09 So, it's another case of unmigrated account, eh? 2023-09-02T02:21:45 malcolmlewis: They try to get away from Geeko, but they always come back. Even after years :~p 2023-09-02T02:31:15 luc14n0, yes, pain in the rear end... 2023-09-02T02:31:37 luc14n0, the hotel geeko it is ;) 2023-09-02T02:52:30 Haha. Indeed. 2023-09-02T05:49:10 there are multiple existing issues for this accou7nt 2023-09-02T05:49:17 I cannot do more with it 2023-09-02T05:49:50 the issue is clearly on the forum 2023-09-02T05:50:02 you need to wipe the user from the discourse database 2023-09-02T05:51:33 if this is not possible you need to reject the tickets, but pls don't pingpong them :) 2023-09-02T14:00:52 acidsys, I cannot touch either the username or email in discourse, it's tied back to IDP, as in they are greyed out, cannot edit, or can but it gets repopulated... 2023-09-02T14:01:26 and we won't delete users else we loose out history 2023-09-02T14:03:32 acidsys, on the account there is this Discourse warning" Users can't be deleted if they have posts. Delete all posts before trying to delete a user. (Posts older than 60 days old can't be deleted.)" 2023-09-02T14:04:46 then if it's not possible they need to make a new account 2023-09-02T14:05:09 I can only change email address and full name in IDP 2023-09-02T14:06:41 acidsys, yes exactly! ;) 2023-09-02T14:17:10 aha, I now know why I never found any users in the discourse database 2023-09-02T14:25:33 malcolmlewis: can you tell me what shows up for either their username or email address in the admin GUI? 2023-09-02T14:25:43 in the database I find an email address entry but no associated account 2023-09-02T14:26:05 in case you do not find either in the admin gui, I will delete the email address entry, which should allow them to log in and automatically create a new associated account 2023-09-02T14:32:34 *** teepee_ is now known as teepee 2023-09-02T14:35:37 acidsys, please do, see if that helps 2023-09-02T14:36:08 can you just check that neither shows up in the GUI? I'm curious to know if the GUI shows users with an user_emails but no user_associated_accounts entry 2023-09-02T14:41:29 acidsys, username an email still there, along with discourse note: Email can be updated from authentication provider. 2023-09-02T14:42:31 okey thank you, I understand, it does show but doesn't let you do anything with it. I'll do my foo then and ask them to try again 2023-09-02T14:43:32 acidsys, this is the old account we are talking about, there is no account present for the new username 2023-09-02T14:45:13 old account but with new email, no? 2023-09-02T14:46:55 old account old email, user wants new username and old email 2023-09-02T14:47:15 well old email equals the email they wish to use 2023-09-02T14:47:45 ok is it possible that was some user impot from pre-idp ? 2023-09-02T14:48:19 also sorry for hijacking your ticket, I didn't notice you updated it in the meanwhile :] 2023-09-02T14:48:56 yes exactly, old account NEVER migrated, they were told cannot be used, in vB I could fix it, now tied to IDP we cannot, plain and simple 2023-09-02T14:49:44 acidsys, which one, user created many ;) I rejected them all except one... 2023-09-02T14:50:26 ok I think I understand now. old account exists, but only in user_emails table, because no login via IDP made it create a matching entry in the user_associated_accounts table. the latter entry cannot be created because an existing user_emails entry with the same primary email address exists. in the GUI you cannot invalidate the old entry because OIDC enabled authentication prevents writing 2023-09-02T14:50:28 to the email field. 2023-09-02T14:50:46 the wrong one, I should have commented on the one you left :b 2023-09-02T14:50:46 the boat has left the dock, no turning back 2023-09-02T14:50:56 thx for consolidating them 2023-09-02T14:51:49 so let's see if this helps now. if it does, I will write "discourse account migration expert" in my CV 2023-09-02T14:52:08 acidsys, which from memory was highlighted way back on the original migration 2023-09-02T14:52:37 if it was known, why was it never considered as a solution pointer ^^ 2023-09-02T14:53:00 acidsys, that worked 2023-09-02T14:54:25 which part 2023-09-02T14:57:23 acidsys, so that was run on the discourse instance? 2023-09-02T14:57:49 database 2023-09-02T14:58:10 acidsys, ahh ok 2023-09-02T14:58:22 when I checked some weeks ago I did not find any entries. now I found there are two equal looking databases, one on localhost one on mirrordb. but the one on mirrordb is the one actively used :P 2023-09-02T15:01:14 acidsys, so on our side we need to deactivate and suspend first so it will send an email to the user, then do the db foo and update the ticket 2023-09-02T15:02:30 which would tell the user it should be good to go, however leaving the domain may try to send an email to the invalid account? 2023-09-02T15:03:16 acidsys, perhaps it should be like we did in vB example.invalid.com 2023-09-02T15:14:04 I think the process is: check for old accounts and invalidate duplicate email addresses, first in IDP, then in Discourse. in case of pre-IDP accounts, Discourse part needs to take place via SQL. 2023-09-02T15:14:19 invalid.com is bad, because it could be registered by a malicious actor at one point in the future 2023-09-02T15:14:52 it would be cleaner to fully delete the old entry or to merge it with the new account. however it will require some additional SQL foo to scan all posts, comments etc for this user_id 2023-09-02T15:27:53 acidsys, why I say let use do the first part is the way it suspends the account is to send an email, this will tell the user it's under action, else it will try to send to a fake account and bounce back to us 2023-09-02T16:33:05 well they get a notification from the ticket anyways 2023-09-02T16:33:31 hey luc14n0 2023-09-02T16:47:44 acidsys, that's not this issue, in Discourse I need to SEND AN EMAIL to the user to suspend the account, so some fake account will cause bounces back to the forum... 2023-09-02T16:48:06 acidsys, it's the way discourse works unfortunately 2023-09-02T16:49:05 Hy acidsys! 2023-09-02T16:49:19 acidsys, my suggestion is wait for the next one, we can come up with a process? 2023-09-02T16:49:45 * malcolmlewis blames luc14n0 for everything including + changes... 2023-09-02T16:52:16 * luc14n0 doesn't know what it is, but swears he's innocent! 2023-09-02T17:20:19 malcolmlewis: surely something that's either configurable or circumentable using SQL ;-) 2023-09-02T17:22:01 * acidsys attests luc14n0's innocence but blames malcolmlewis for no changes 2023-09-02T17:24:37 \o/ 2023-09-02T17:26:24 acidsys, oh for sure, I'm just worried about discourse getting all confused... 2023-09-02T17:26:47 and we start getting bounced emails... 2023-09-02T17:27:24 hmm I see well maybe I do the merging sql foo some time then 2023-09-02T17:29:36 acidsys, maybe can include a disable the account in the sql foo 2023-09-02T17:44:23 * luc14n0 can't push changes to his own repo in src.opensuse.org, what's going on! 2023-09-02T17:46:36 Oh, smells like a misconfiguration. It fails to authenticate. 2023-09-02T17:47:07 * luc14n0 tries to find someone to blame! 2023-09-02T17:48:34 it's in buildservice' jurisdiction 2023-09-02T17:49:15 maybe adrianS knows about src.o.o (or about whom to ask) ? 2023-09-02T17:50:10 Yeah, I know I can blame Dirk, but they're still on vacation until next week :~P 2023-09-02T17:51:45 Wanted to experiment setting up a CI for GNOME packages, but that'll have to wait now. 2023-09-02T18:21:08 ah, right Dirk would know 2023-09-02T19:03:28 Dan might know too, but it's weekend. 2023-09-02T23:13:22 *** teepee_ is now known as teepee