Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ Bug ] Disabling email login break Python token generation script #136

Open
gwright99 opened this issue Jul 25, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working

Comments

@gwright99
Copy link
Collaborator

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.

@gwright99 gwright99 self-assigned this Jul 25, 2024
@gwright99 gwright99 added the bug Something isn't working label Jul 25, 2024
@gwright99
Copy link
Collaborator Author

gwright99 commented Jul 25, 2024

As per Seqera Engineering:

  • 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.
  • The token script calls this endpoint to initiate the token generation.
  • 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

  1. 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.

  2. 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.

  3. Other solution?

Potential Long-Term Workarounds

  1. Have Tower generate a root PAT on first invocation (like Gitlab).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant