You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting flag_disable_email_login = true causes an error to be returned by the {TOWER_API_ENDPOINT}/gate/access endpoint if called with an email address.
OIDC flow as a replacement is a non-starter -- this would be happening on an instance with a pre-existing IDP session.
Potential Short-Term Workarounds
Don't allow flag_run_seqerakit = true if flag_disable_email_login = true
Automation logic would not need to change, but it means seqerakit could not be run on the very first deployment.
Boot Tower with email enabled, generate a token, stop Tower, update tower.yml to disable email, reboot Tower, run Seqerakit.
This is super clunky and I hate it. Multiple new branches of logic will need to be created.
Other solution?
Potential Long-Term Workarounds
Have Tower generate a root PAT on first invocation (like Gitlab).
Setting
flag_disable_email_login = true
in terraform.tfvars appears to cause the _get_access_token.py script to fail.The script does not fail when email is allowed.
The text was updated successfully, but these errors were encountered: