Open Settings, choose Git Access and click Verify. Cyberlop tests the token you saved. Save a new token first if you just pasted one. If the check fails, look at the token's read access and the Allowed hosts list.
Steps
The status pill reads A Git token is configured. when one exists. It does not say the token still works, so run Verify to find out.
STEPSIf Verify fails
Work through these checks in order.
| Check | What to look for |
|---|---|
| Read access | A read-only token with access to the repository, as the warning box describes |
| Allowed hosts | Your code host's domain is in the list |
| Token life | The token has not expired or been revoked at your code host |
Good to know
Cyberlop encrypts the token at rest and never shows it again, so you cannot look at it to see what went wrong. Paste a fresh one into Replace token and save.
Passing here does not rule out trouble, because a token can still fail on one repository if it lacks access to that repository alone. Test a real clone by running a scan on a small white-box target.
For the full setup, read how to add an organisation Git token. When you are stuck, tell us on the contact page.
Run Verify at set moments: after you paste a token, after your code host rotates or expires one, and whenever a white-box scan cannot clone a private repository. Tokens can lapse quietly, and the pill will not warn you. Checking takes one click and saves you a failed scan later in the week.
Related questions
- How do I add an organization Git token for private repositories?
- How do I limit which hosts the Git token is sent to?
- How do I remove the organization's Git token?
- What permissions should my Git token have?
- How do I add my own personal Git token?
Git access in Cyberlop: set a read-only token and allowed hosts
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Still stuck?
Tell us what you see on screen and an engineer will help you sort it out.