[Action Required] Github SSO for traveloka organization
Overview
We are enabling SSO for traveloka Github organization. Please start authenticate and authorizing your key using Google account before Aug 08, 2022.
Failed to authenticate before Aug 08, 2022 will result access lost to Traveloka Github organization.
Who is this announcement for?
For all engineers that are using Github in traveloka organization
What do you need to do?
- Go to github.com/orgs/traveloka/sso, press authenticate button to join Traveloka organization and initiate the process.
- Go to github.com/settings/keys, authorize all keys that you're using for work-related activity in
traveloka organization
- For detailed steps, please follow this article
- Go to github.com/settings/tokens, authorize all tokens that you're using for work-related activity in
traveloka organization, including tokens for automation.
FAQ
- Why I can't authenticate to Traveloka Organization?
- You're email hasn't been granted Github access. Open ticket to CorpIT to request the access.
- Why
gh CLI is no working?
- Please re-authenticate using:
gh auth login
- Why Github mobile app is not working?
- Log out and relogin to authenticate with SSO.
Why is this needed?
Add another security layer to ensure only active employee has access to our code base.
Timeline
- Monday, Aug 08, 2022, SSO will be required in
traveloka github organization
Questions/Concerns?
Please contact the Cloud Infra team through #site-infra-channel and through Jira Service Desk [1].
Darwin Wirawan, on behalf of the Cloud Infra Team