Change 1006178 had a related patch set uploaded (by Gergő Tisza; author: Gergő Tisza):

[mediawiki/extensions/CentralAuth@master] Show temp user status on Special:CentralAuth

https://gerrit.wikimedia.org/r/1006178

In hindsight a better way to do this would be T359064: Decide if we want to represent temporary account expiry with system blocks (and then some version of T358979: Show global block information on Special:CentralAuth/<username>).

Change #1006178 merged by jenkins-bot:

[mediawiki/extensions/CentralAuth@master] Show temp user status on Special:CentralAuth

https://gerrit.wikimedia.org/r/1006178

Status quo from testwiki:

cc @Niharika @KColeman-WMF, something for us to discuss from a product, design and technical direction.

The page is different when the temporary account is expired. This is because a "Temporary account expired" bullet point is added to the "Global account information" box. An example is below:

@kostajh moving to radar - in case you need our help please ping us.

@KColeman-WMF @Niharika this needs some design and product input.

Looking at:

I would propose we add a line for Temporary account expiry date: 19 December 2024 (registration date + maximum temp account age in configuration)

And then I think we could resolve this task. What do you think?

In T357935#10163678, @kostajh wrote:

@KColeman-WMF @Niharika this needs some design and product input.
I would propose we add a line for Temporary account expiry date: 19 December 2024 (registration date + maximum temp account age in configuration)

Would this replace the line that already exists but is only shown when the temporary account expires:

In T357935#10163699, @Dreamy_Jazz wrote:

In T357935#10163678, @kostajh wrote:

@KColeman-WMF @Niharika this needs some design and product input.
I would propose we add a line for Temporary account expiry date: 19 December 2024 (registration date + maximum temp account age in configuration)

Would this replace the line that already exists but is only shown when the temporary account expires:

No, we'd keep that line.

Although, maybe showing expected expiry is not really useful. I can't imagine what someone would need it for at a glance, and it's easily mentally calculated.

What is the user story / use case for wanting to see an expected expiry of a temp account on this page?

@kostajh - one question that got me thinking - I assume that expiryAfterDays won't be changed often, but it probably won't change at all. Do we foresee any scenarios when this value gets changed on prod? If we increase it - is it going to "re-enable" all temp-accounts that were previously expired but are still "active" ?

In T357935#10164184, @pmiazga wrote:

@kostajh - one question that got me thinking - I assume that expiryAfterDays won't be changed often, but it probably won't change at all. Do we foresee any scenarios when this value gets changed on prod? If we increase it - is it going to "re-enable" all temp-accounts that were previously expired but are still "active" ?

I suspect that if anything, we would decrease the default value (90 days). But if we increase it, there's no impact on expired temp accounts -- they are already logged out, session invalidated, and no way to get back into their account.

In T357935#10163798, @KColeman-WMF wrote:

What is the user story / use case for wanting to see an expected expiry of a temp account on this page?

People who are not yet familiar with temporary accounts (which will be most people at first) might benefit from a reminder that the account is temporary, will expire in X number of days, etc. But we'd probably be fine not including this additional information here.

I'm on the fence about it. It's possible the user got rid of the cookie accidentally and the account already "expired" but we can't reliably indicate that.

I see Kosta's point about reminding users that this is a temporary account but I think this page is likely only to be used by active functionaries who should already be familiar with the concept of temp accounts.

In T357935#10163699, @Dreamy_Jazz wrote:

In T357935#10163678, @kostajh wrote:

@KColeman-WMF @Niharika this needs some design and product input.
I would propose we add a line for Temporary account expiry date: 19 December 2024 (registration date + maximum temp account age in configuration)

Would this replace the line that already exists but is only shown when the temporary account expires:

Is that line also shown when the temp account hasn't expired yet?

In T357935#10166838, @Niharika wrote:

I'm on the fence about it. It's possible the user got rid of the cookie accidentally and the account already "expired" but we can't reliably indicate that.

I see Kosta's point about reminding users that this is a temporary account but I think this page is likely only to be used by active functionaries who should already be familiar with the concept of temp accounts.

In T357935#10163699, @Dreamy_Jazz wrote:

In T357935#10163678, @kostajh wrote:

@KColeman-WMF @Niharika this needs some design and product input.
I would propose we add a line for Temporary account expiry date: 19 December 2024 (registration date + maximum temp account age in configuration)

Would this replace the line that already exists but is only shown when the temporary account expires:

Is that line also shown when the temp account hasn't expired yet?

No. Only shown after the temporary account should been have expired based on the expiry configuration.

@Niharika wrote:

I think this page is likely only to be used by active functionaries who should already be familiar with the concept of temp accounts.

This is my assumption too therefore I don't think we need to include the line about expiry, unless it's already expired (as in the example from @Dreamy_Jazz) Happy for this assumption to be challenged though!

In T357935#10167242, @KColeman-WMF wrote:

@Niharika wrote:

I think this page is likely only to be used by active functionaries who should already be familiar with the concept of temp accounts.

This is my assumption too therefore I don't think we need to include the line about expiry, unless it's already expired (as in the example from @Dreamy_Jazz) Happy for this assumption to be challenged though!

Yeah, I can see that side. OTOH I would assume that people will be unsure and unfamiliar with temporary accounts at launch, and probably for a long time afterward, and I wouldn't expect functionaries to remember details like the configuration set for the expiration. But, yeah, this is all quite minor, so I am fine to leave it out of the UX until someone from the wikis asks us to add it.

Can we close this task for now? We denote whether a temporary account has expired on Special:CentralAuth. The other idea of showing the expected date for expiry seems to be something we would add only if asked for it. I'm not sure what else we would do for this task, given that the task description only mentions showing the expiry for the temporary account.