Problem in github student developer pack #184243
Replies: 1 comment
-
|
Registration Credentials (. credentials file) When you register a self-hosted runner, it generates an RSA key pair that is stored in the . credentials file. This RSA key does not have a set expiration or TTL. It remains valid indefinitely until you manually remove the runner or revoke its registration. Job-Scoped OAuth Access Tokens The runner uses those registration credentials to request OAuth access tokens for each job. These job-scoped tokens have a TTL of the lifetime of the job run, or the job timeout setting (default is 6 hours), plus 10 additional minutes. So the maximum TTL for a job token is approximately 6 hours and 10 minutes by default. For Your Use Case Since you want hardware available only during a short time window, here are some approaches:
For more technical details, you can review the runner authentication design documentation at https://github.com/actions/runner/blob/main/docs/design/auth.md |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I previously had a GitHub student account with the GitHub Student Developer Pack (Pro). Unfortunately, I lost access to my authenticator app, so I couldn’t log in due to 2FA. Because of this, I unlinked my college email and created a new GitHub account.
Now, when I try to apply for the GitHub Student Developer Pack using the same college email on my new account, GitHub shows that the email is already linked to another account.
How can I resolve this issue? Is there a way to fully unlink the student pack from the old account or recover access without the authenticator app?
Beta Was this translation helpful? Give feedback.
All reactions