How long is the TTL of the OAuth token stored in .credentials on a self-hosted runner after registration
#184232
-
Why are you starting this discussion?Question What GitHub Actions topic or product is this about?General Discussion DetailsI want a subset of hardware to be available for jobs during a short time window |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
I did run self hosted runners for over a year i think without the token expiring. If you want to time the access of a runner i think you need to programmatically register it and also stop + unregistered it via API and also via the script on the machine it is running on. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
I did run self hosted runners for over a year i think without the token expiring.
As far as i understood from researching the "token" in .credentials is just the registration token (when you first register the runner).
After the registration it has obtained a public private key pair which the runner uses to authenticate. And this doesn't have a TTL as far as i know.
If you want to time the access of a runner i think you need to programmatically register it and also stop + unregistered it via API and also via the script on the machine it is running on.