Saltar al contenido principal

Connecting Forgejo to Your Application

You will configure a personal access token on your Forgejo instance and provide it to Plexicus so it can scan your repositories.

Forgejo is a personal-access-token connector: it performs no OAuth redirect, so there is no callback URL to register and no client id or secret to configure — on Plexicus SaaS or on a self-hosted deployment. The token needs repository read for discovery, cloning and scanning, user: read so Plexicus can verify it against your instance's /api/v1/user endpoint, and repository write if you want remediation pull requests.

Prerequisites​

  • Access to your Forgejo instance (self-hosted or forgejo.io)
  • At least one repository with source code
  • Admin or user permissions to create a personal access token

Steps​

1. Access the Connectors page​

Log in to your Plexicus account and navigate to Integrations → Connectors.

2. Select Forgejo​

In the SCM section, locate the Forgejo card and click Configure.

3. Generate a Forgejo personal access token​

On your Forgejo instance:

  1. Click your profile icon (top-right corner)
  2. Select Settings
  3. Go to Applications
  4. Click Generate New Token
  5. Name the token (e.g., plexicus)
  6. Select scopes: repo (or the equivalent "Full control of private repositories")
  7. Click Generate Token
  8. Copy the token immediately — you won't see it again

4. Provide Forgejo connection details to Plexicus​

In the Plexicus Forgejo connector form, fill in:

  • Forgejo URL: https://your-forgejo-instance.com (or your Forgejo domain; e.g., https://forgejo.io)
  • Personal Access Token: Paste the token you just generated

5. Test the connection​

Click Test Connection to verify that Plexicus can access your Forgejo instance.

6. Save and finalize​

Click Save or Connect. Plexicus will discover and list your repositories.

Verify​

In Plexicus, go to Assets and check that your Forgejo repositories now appear in the list. You can now create scans against them.

Troubleshooting​

"Connection failed" / "Invalid credentials"

  • Verify the Forgejo URL is correct and reachable from Plexicus
  • Confirm the personal access token is still valid and has repo scope
  • If self-hosted, check network connectivity and firewall rules

Repositories don't appear

  • Ensure the token has repo scope
  • Verify you have at least one repository in your Forgejo instance

Next Steps​

You can now create an application using Forgejo as your Source Control Management (SCM) system. See Creating and managing applications to get started.