Access token not visible/generated

[Mestizia]

I am previously generated 2 access tokens, now I am trying to setup a third one but it does not show after creation (see red circle):

If I refresh the page it only shows 2 in the circled area.

[TetraW]

Hello, sorry for the late response.
I have just tested creating and deleting some personal access tokens, which worked for me.

Does the problem still persist?

[Brilator]

Happened for another user as well. Cannot reproduce currently.

[j-bauer]

It would help to know the userid and an approximate timestamp to check the logs. Should be on another channel, like teams.

[j-bauer]

The DataHUB was updated since this issue was created. Does the problem still occur?

[Brilator]

Comment from a user today:

I was trying to create a personal access token in my profile on the https://git.nfdi4plants.org/ page. After going through the process to create an access token, I would see a message stating "Your new project access token has been created" and see that the number had changed indicating that 1 access token was active for my project, however, there would be no access tokens below. After refreshing the page, the number would change back to 0, and the page would look the same as before going through the access token creation process. I experimented a bit, and it seems that the maximum length of time that an access token can be active before expiration is one year, otherwise the token will not be created. However, there was no error message stating this, or no time limit visible in the creation page that would indicate this, which was confusing.

So I guess, the issue persists.

[j-bauer]

That's valuable feedback, thanks! I will look into the expiration date and see if that is indeed the problem.

Edit: I could reproduce the issue with tokens > 1 year. This issue is also known and is being worked on: https://gitlab.com/gitlab-org/gitlab/-/issues/432403

[TetraW]

It looks like this is an issue with the current GitLab version the DataHUB runs on. This should be fixed after the update during the next maintenance break, which we intend to carry out next week. If an access token with an invalid expiration date is specified, it will then look like this: