Skip to main content

GitHub Authentication with SAML Single Sign-On for AIQ

GitHub Authentication with SAML Single Sign-On for AIQ

Use this article when AIQ or related CI/CD workflows need to access a GitHub organization that enforces SAML single sign-on. Validate authentication and authorization before using the workflow in scheduled runs.

Configuration checklist

  • Confirm the GitHub organization, identity provider, and user or service identity that needs access.
  • Authorize the GitHub token or app for the SAML-protected organization.
  • Use least-privilege repository access and avoid personal administrator credentials for automation.
  • Store tokens in secured variables or a secret manager, not in AIQ steps, scripts, or logs.
  • Document token owner, expiration, rotation process, and support contact.

Validation workflow

  1. Confirm SAML authorization in GitHub for the target organization.
  2. Run a small read-only repository operation first.
  3. Validate the CI/CD or AIQ integration path that requires GitHub access.
  4. Review logs to confirm no token or SAML details are exposed.

Last updated: October 10, 2026

Back to top