Use your Beskid account
Authentik handles browser sign-in for protected Beskid services through the shared Caddy edge. Tracker and Nexus require a session. Learn and pckg keep their public catalogues available without one.
Prerequisites
Section titled “Prerequisites”Use a browser, an internet connection, and a GitHub account that you can sign in to. Do not send cookies, tokens, or private responses in a public support request.
Actions
Section titled “Actions”- Open Tracker or another protected Beskid service.
- Verify that the redirect reaches Authentik at
https://auth.beskid-lang.org. - Complete GitHub OAuth when Authentik offers that sign-in method.
- Return to the selected service after authentication.
Expected result
Section titled “Expected result”GitHub OAuth returns you to the selected service with a signed-in account. Access remains subject to that service’s authorization rules.
Recovery
Section titled “Recovery”If sign-in does not return to the service, record the visible sign-in error and the public route. If the problem continues, use the Authentication operator contract for service availability and authorized recovery. Do not ask an operator to disclose a secret.
Next task
Section titled “Next task”Open Read Tracker for delivery status, or Explore Nexus for a repository graph after sign-in.