Closed blairlyons closed 1 year ago
I believe this is something that a simple configuration change to our github enterprise settings will fix (based on reading this). However, I do not have an admin account so I can't do this independently. I'll go to Software Engineering Office Hours on Wednesday and try to get this sorted
Tracked in ServiceNow ticket: INC0011051
Alright everything is all good! The last step was updating the relevant personal access tokens associated with secrets referenced in the actions to have SSO properly configured. I just generated a new personal access token and updated the simularium secret, and now that seems to be all good! If there are any other actions that are failing that use a different secret, all one has to do is make sure the token that is affiliated with it has single sign on authorized for the relevant project.
What needs to happen?
With recent changes to linking github accounts for the institute, a bunch of actions are failing with: "Resource protected by organization SAML enforcement. You must grant your Personal Access token access to this organization." I'm not sure if this needs to be done on a per account basis, if that's the case we need instructions for everyone on how to do this.
Why should we do this?
We need our actions to work.
When does this need to get done?
Early July 2023