Create an access token

Your Git client asks for a password, and the wiki password does not work.

Git access has separate, personal access tokens. They are created in self-service, apply to your account and can be withdrawn individually without changing the wiki password.

1. Sign in to the wiki. Without a session the self-service page is unreachable.
2. Open Access tokens.
3. Give it a label naming its purpose — the machine or the tool that will use the token, say.
4. Create the token.
5. Copy the value shown at once and put it where your Git client keeps credentials.

The value always begins with wkg_. That is how you recognise it again in a credential store — and how a search for accidentally published credentials recognises it too.

The value is shown exactly once. Only a hash is stored; nobody — not even somebody with administration rights — can read it out later. Where it is lost, withdraw the token and create a new one.

A token is a password. It authenticates as your account and carries its permissions. Do not pass it on and do not put it into a repository.

One token per purpose. Several tokens with meaningful labels can be withdrawn individually; a single token for everything forces every client to be set up again on any suspicion.

Withdrawal takes effect at once. The endpoint checks anew on every call and holds no result. A withdrawn token fails on the next fetch, not after some waiting period.

Issuing may demand an extra confirmation. Where a raised assurance level is configured for token issuing on this installation, the page leads there first. That affects only creating, not using an existing token. A later tightening likewise affects only new tokens — those already issued keep their validity until somebody withdraws them.

When authenticating in the Git client the user name does not matter. The token belongs in the password field; see Clone a repository.

• Clone a repository
• Set up a development environment