GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.

Two-factor authentication (2FA) is now required for all NEA GitLab users. This will require any users of the system to follow the online instructions to setup 2FA from their user profile:

Additional documentation is provided here:

Two factor authentication · Account · Profile · User · Help · GitLab

The process is very straightforward and supports standard applications including Microsoft Authenticator, Google Authenticator, and others. Users that programmatically interact with the NEA GitLab (e.g. with the GitLab API) will be able to create personal access tokens (PATs) with well-defined scopes that must be limited to those required for their use. Please note the tokens expire by design and may never be shared with others. More documentation is provided here:

Personal access tokens · Profile · User · Help · GitLab

Thank you for your co-operation and continued support of cybersecurity standards at the NEA.

EXFOR

OECD Nuclear Energy Agency GitLab

Admin message

Admin message

EXFOR