Some GRSciColl mediators are in suggestion mode even when logged in

[ManonGros]

This is an issue reported both by @vijaybarve and @spalp

@spalp mentioned that when she started a suggestion, then cancelled and logged in and click on the edit button again, she wasn't able to save the change. This is a screenshot she sent:

When talking to @vijaybarve, I thought the issue was that he was logged out while editing but maybe he had the same issue as Salza.

Vijay and Salza, don't hesitate to comment if you would like to add more details. Thanks!

[MortenHofft]

It would be helpful with more context. What are the roles/usernames of the users. what entities are they trying to edit. Is it always an issue or does it require a special list of actions to trigger?

[MortenHofft]

I'm guessing that it is spalpurina and

must be this collection https://registry.gbif.org/collection/e2c01c12-4e38-42bd-8c5f-e53c1bc66b74 ?
I cannot see the full uuid. And it has a different description, but the uuid ends in the same chars and the names are the same.

[MortenHofft]

I see it was last edited 5 hours ago by that user. So what did she need to do to fix it? i cannot reproduce it. Can you or the user?

From above I have no idea I'm afraid. A caching issue on the authentication endpoint perhaps?

[ManonGros]

Both Salza and Vijay are GRSciColl Mediators. They both tried to edit entries that belong to countries within their scope. Instead of being able to edit the entries directly, a suggestion was logged and sent.
Then both of them had to go and apply to suggestions. Like this one: https://registry.gbif.org/collection/e2c01c12-4e38-42bd-8c5f-e53c1bc66b74?suggestionId=1461

I myself haven't encountered the issue.

[spalp]

From above I have no idea I'm afraid. A caching issue on the authentication endpoint perhaps?

Does this help? Working on the same entry on another machine: https://registry.gbif.org/collection/e2c01c12-4e38-42bd-8c5f-e53c1bc66b74, when I repeated the same steps (i.e. started a suggestion, then cancelled and logged in and click on the edit button again), I was able to save succefully the changes.

[MortenHofft]

thank you. I will try that

[MortenHofft]

Oh, rereading that I see that it works in above example. I'm more interested in a repeatable example where it fails.

The cache headers look right. So probably not a caching issue.
I created a user with the same rights, and cannot reproduce any errors.
It makes it difficult to fix.

@spalp if you can, it would be great with a reproducible error example

[vijaybarve]

I guess the issue is with timeout. I guess, if I take more time to make all the edits it takes me to suggest, but if I submit after every one or two edits, it lets me do it.

[MortenHofft]

That is useful information and a likely cause @vijaybarve - thanks

The API signs you out automatically after x minutes. @marcos-lg you know the logic of this. The UI tries to compensate for this by signing in on every authenticated request. But if the UI is left unused (or you fill a form for 30 minutes), then there is no API interaction and hence the token isn't renewed.