Chameleon Authentication Demystified: Common Issues and Solutions
Navigating Federated Identity, Multiple Accounts, and Common Pitfalls
- Sept. 15, 2025 by
- Paul Marshall
Don't let authentication problems derail your research momentum. This practical guide demystifies Chameleon's login system and arms you with clear, step-by-step solutions for the authentication challenges that frustrate users most. Learn to confidently navigate multiple accounts, identity provider changes, and stubborn login issues.
Photo by Markus Spiske on Unsplash
Account Basics
Getting started with Chameleon is straightforward thanks to our federated authentication system through Globus. Most users can sign in using credentials they already have through their institution—no need to create yet another username and password.
When you visit Chameleon and click "Sign in via federated login," you'll be redirected to Globus where you can select your institution (or another identity provider like GitHub or Google) to authenticate. Once authenticated, Globus maps your account to a unique Chameleon account, and you're ready to go.
Important: If you previously used TACC federated identity to access Chameleon, note that this authentication method has been deprecated and will no longer be available as of January 2026. Please follow the steps outlined in our changelog to migrate your account to Globus authentication.
For detailed guidance on account setup, getting allocations, adding users to projects, and understanding day passes and anonymous access options, see our comprehensive user documentation.
Technical Details
Under the hood, Chameleon auth is federated with Globus. What this means practically is that when you login to Chameleon, you are actually redirected to Globus where you can select an identity provider, such as your institution (or Globus itself as an identity provider if you have a Globus account), and login.
The Globus login flow after clicking "Sign in via federated login:"
Once authenticated through Globus (and possibly your institution or another valid identity provider, such as GitHub or Google) your Globus account is mapped to a unique account on Chameleon. Chameleon doesn't manage your underlying account with your password at all!
After successful login via Globus, Chameleon creates an authenticated session for you, which grants you access to certain portions of Chameleon based on your permissions.
Managing Multiple Accounts & Identity Changes
Users sometimes find themselves with multiple accounts or need to change their primary login method. Here are the most common scenarios and solutions:
Multiple Institutional Accounts
If you have accounts at different institutions and need access to the same Chameleon projects, account merging is typically not necessary. Instead, the recommended approach is to have your project PI add your additional account to the existing project. This grants access without requiring complex backend changes.
For example, if you started a project using your university email but now need access from a different institution, simply ask your project administrator to add your new institutional account to the project rather than attempting to merge accounts.
Changing Your Primary Identity Provider
If you've switched your primary GitHub/Google account or changed institutions and want to update your Chameleon login method, you can manage this through your Globus account settings:
- Visit your Globus identity settings
- Link your new identity provider (GitHub, new institution, etc.)
- Set it as your primary identity if the option is available
- Clear your browser cache and reauthenticate via Chameleon's federated login
To verify which identity provider you're currently using, check your Globus identity settings page—your primary identity will be clearly marked, and you can see all linked accounts.
If you cannot change your primary identity through the Globus web interface, contact Globus support directly for assistance.
When You Can't Access Your Account
If you're having trouble accessing projects you should have permission for, first verify you're logging in through the correct identity provider. It's easy to accidentally sign in through a different account than the one linked to your Chameleon projects.
Common Pitfalls
Federation for auth can be a point of confusion for many. It comes with a few key caveats worth calling out:
- Chameleon doesn't store your password. Because Chameleon federates auth, we don't have your password and can't ever reset it if you forget it. For that you need to contact your identity provider, such as your home institution, to help reset and manage your credentials.
- Stale cookies. Federated auth relies on cookies to manage your login state and these cookies can become out-of-sync, stale, or corrupt, which can prevent login. The easiest solution is to just clear your cookies and login again or try logging into Chameleon with a different browser whenever the login flow isn't working correctly. More often than not this resolves cookie-related issues.
- Using the wrong account. Users sometimes have multiple accounts that they've used with Chameleon and they forget to sign in their Globus-linked account through their institution. If you are having trouble logging in make sure you are following the Globus auth flow and signing in through your institution or another Globus-supported identity provider.
- Identity provider confusion. When switching between different identity providers (like moving from one GitHub account to another), make sure you're managing the change through your Globus account settings first, then clear your browser cache before attempting to sign in to Chameleon.
Need Help?
If you're experiencing authentication issues that aren't resolved by the troubleshooting steps above, our support team is here to help. Most account-related issues can be resolved quickly with the right guidance from our help desk.
Remember: for password resets and primary account management, you'll need to work with your identity provider (your institution or Globus directly). For project access and Chameleon-specific permissions, our support team can assist you or connect you with the right project administrators.
The key to smooth authentication with Chameleon is understanding that we leverage the accounts you already have—making it easier for you to get started with your research without managing another set of credentials.
Chameleon Changelog for August 2025
- Sept. 3, 2025 by
- Mark Powers
New H100 hardware on KVM@TACC, and good news about KVM lease limits, quotas, and SU cost. Additionally, we have SU changes for baremetal, an improved the resource browser, and are announcing the deprecation of TACC login.
Experiment Pattern: Bastion Host
The easiest way to deploy a secure cluster for scientific research
- Jan. 23, 2023 by
- Adam Cooper
We go over the benefits of using a bastion host to administer your cluster. It's the easiest way to deploy a secure cluster of hosts for your experiments, and it also helps to save resources!
Chameleon Access via Federated Login Coming Soon!
- Oct. 5, 2020 by
- Kate Keahey
The way you access the testbed will change -- for the bettter! You will be able to access the testbed via federated login allowing you to log in with your instritutional credentails or even your Google account -- read about the impact and schedule of this important change!
No comments