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, Organization → Read
(read:organization) so it can list organizations and you can pick an owner,
and repository write if you want remediation pull requests. A token that can
sign in but cannot list organizations is not enough.
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. Open Settings › Integrations
Log in to your Plexicus account. In the left sidebar, click Settings, then Integrations.
2. Select Forgejo
Select the SCM category, locate the Forgejo card and click Configure.
3. Generate a Forgejo personal access token
On your Forgejo instance:
- Click your profile icon (top-right corner)
- Select Settings
- Go to Applications
- Click Generate New Token
- Name the token (e.g.,
plexicus) - Select repository: read, user: read, and Organization → Read
(
read:organization). Add repository: write if you want remediation pull requests. A singlereposcope is not a substitute for Organization → Read. - Click Generate Token
- 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
reposcope - If self-hosted, check network connectivity and firewall rules
The token can sign in, but organizations do not list
- Edit the token and enable Organization → Read (
read:organization), then save the connector again - A token that only has
repo(or user read) can pass sign-in and still be refused here
Repositories don't appear
- Ensure the token has repository read, and Organization → Read if the repositories belong to an organization
- 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.