The token field stays blank after saving. How can I tell whether my Git token saved?

Why this happens

Cyberlop encrypts every secret at rest and never shows it again after you save. That is why the password field looks empty or shows dots. The page tells you to leave it blank to keep the current value. A blank field does not mean the save failed.

How to fix it

1. Go to Settings → Git Access. Read the status pill at the top. A saved token turns it to "A Git token is configured."
2. Press Verify to test the saved token. The field stays blank, and that is normal.
3. Look at Allowed hosts. The token is only sent to the hosts listed there.
4. For a token you saved yourself, open My Account. The status at the right of the Git access token card should no longer read "Not set".
5. Run a scan on a white-box target with a private repo. If it clones, the token works.

If you press Save Git settings with the field blank, Cyberlop keeps the stored token. Use Clear token only when you want to remove it.

Still not working?

When the pill says no token exists, paste the token again and save it. If Verify fails, check that the token has read-only access to the repository and that the repo host appears under Allowed hosts. Cyberlop clones a repository on any other host without the token, as if it were public. More help: verify a Git token, a private repo that will not clone and why saved secrets stay hidden. You can also use the contact page.

Related questions

• How do I add an organization Git token for private repositories?
• How do I check that my Git token works?
• Why can't I see my saved token or key any more?
• How do I add my own personal Git token?
• What's the difference between my personal Git token and the organization's Git token?

Full tutorial

Git access in Cyberlop: set a read-only token and allowed hosts

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre