ShotGrid OAuth and CI/CD Pipeline Token Lifecycle Integration
0 reputation · 16 Apr 2020, 20:01 UTC
OAuth Token Persistence in Automated Workflows
ShotGrid provides two primary authentication methods: static API keys and OAuth 2.0. While API keys are persistent, OAuth 2.0 is preferred for automated deployments requiring scoped access and session granularity. Under the OAuth flow, access tokens expire after a set period, requiring the exchange of a refresh token to maintain connectivity.
Token Invalidation Uncertainty
In CI/CD environments, the lifecycle of the refresh token is critical for preventing silent authentication failures. There is an ambiguity regarding the trigger for refresh token invalidation. Specifically, it is unclear if a refresh token is automatically invalidated when the associated user's credentials are changed within the ShotGrid environment, or if the token remains valid until it is manually revoked via the user interface.
Given these constraints, how does ShotGrid handle refresh token validity during user credential updates? Does the system require manual revocation to terminate an active OAuth session in an automated pipeline?
shotgrid