Authentication Service Provider Migration
min

Authentication Service Provider Migration

To continue improving security and reliability, Solsta is migrating its authentication service from Auth0 to Cognito on June 26, 2026. The move will enable enhanced security features such as passkeys and account takeover protection (more details below).  

What you need to know

  • Maintenance window: June 26, 2026, 6:00–10:00 PM PDT  
  • Expected impact: brief authentication interruptions; deployments, installs, and updates may be intermittently affected during the maintenance window.
  • Required action before June 26: update Solsta CLI if using user login  
  • Recommended action before June 26: update your SSO redirect URI and test Cognito SSO  
  • Required action by August 28: complete the transition from Auth0-based user login and old M2M credentials to the new Cognito-based authentication flow

Our goal is to complete this migration with minimal disruption to Solsta access, deployments, installs, and updates. Please see the table below for recommended actions before and after the migration period.  

Yes = action required No = no action needed by that date
Action Applies to Requiredby June 26? Requiredby Aug 28? Notes
Add Cognito SSO redirect URI SSO implementations No Yes Recommended before June 26 to simplify login
Generate new M2M credentials CI/CD and automation users No Yes Old Auth0 M2M credentials retire Aug 28
Update deployment tools / plug-ins CI/CD users No Yes Required to use new Solsta 2.1 credentials
Update Solsta CLI to 8.0.46 for user login CLI users using user credentials Yes Yes Required for compatibility with backend changes
Update Desktop Application GUI users Yes* N/A Users will be prompted to self-update

*A required update will be presented to GUI client users starting June 26.  Failure to apply this update will result in client errors.


What happens if no action is taken before June 26?

This is a quick summary. Additional details in the sections below.  

  • SSO customers can continue using the existing Auth0 flow during the transition period, but users may need to enter the organization slug twice.  
  • Existing M2M credentials will continue working temporarily.  
  • Auth0-based M2M credentials will be retired on August 28, 2026.
  • Users of the Solsta CLI with user credentials must update to version 8.0.46 to log in after the migration.  

Client Updates for All Users


Solsta Desktop Application (GUI)
will notify and prompt users to accept a self-update on new sessions after the migration window. This update is required.  

Solsta CLI – download version 8.0.46 from the downloads page

  • This update is required if logging in with user credentials
  • If logging in with M2M credentials:  
  • Solsta CLI 7.2.185 supports existing Auth0-based M2M credentials during the transition period
  • Solsta CLI 8.0.46 supports new Cognito-based M2M credentials created in Solsta 2.1

CI/CD Updates for DevOps Users


Machine to Machine (M2M) Credentials

After June 26, users with the Organization Admin role will not be able to see existing M2M credentials in the Solsta 2.1 Desktop Application, but those credentials will continue to work for deployments.  

We recommend you do the following at your earliest convenience:  

  • Assign the new machine a role (example: Organization Admin or Product Admin)
  • Update the deployment executables or plug-in in your CI/CD system (details below)
  • Swap your existing credentials in your CI/CD system
  • Notify Solsta support so we can retire your old credentials

Existing Auth0-based M2M credentials will stop working after August 28, 2026.

Deployment Tools for CI/CD Integrations

Once you generate new machine credentials in Solsta 2.1, you will need to update your deployment executables or plug-in to use them.  

Component Version Link
Deployment Executables – Windows 4.0.15 Download
Deployment Executables – Linux 4.0.15 Download
Jenkins Plug-in 1.73 Download
TeamCity Plug-in 1.77 Download


Notes  

  • A QuickBuild plug-in compatible with new credentials will not be supported. Please use the deployment executables within QuickBuild instead.  
  • Machine credentials generated in Solsta 2.1 will NOT work with previous versions of the deployment tools or plug-ins


For Organizations Using Single Sign-On  


To transition your SSO integration to Cognito and simplify the Solsta login flow, add the new redirect URI to the Solsta application within your SSO system:  

https://oauth.snxd.com/oauth2/idpresponse

Do not replace the existing redirect URI at this time.  

After you add the new redirect, notify the Solsta support team via:  

Please include the following in your support ticket:  

  • Organization name / slug  
  • SSO provider  
  • Confirmation that redirect URI was added  
  • Preferred technical contact

Once we receive your support ticket, we will reply with a unique login URL for your organization so that you can test the new SSO integration.  

On migration day, we will enable the Cognito login alongside your existing SSO integration login via Auth0 to prevent any disruptions in service. This means you will have dual login options for a time.  

Once your team has confirmed the new Cognito integration is working with the Solsta 2.1 client, we will remove the old Auth0 option from your configuration.  


If you do not add the redirect and test your Cognito SSO integration by June 26, 2026, your existing SSO integration will continue to work in Solsta 2.1, however, the process will entail entering your organization slug twice:  

  1. Enter org slug from within Solsta UI
  1. Select Auth0 login option
  1. Enter org slug in the Auth0 organization prompt
  1. Log in to your SSO provider

Example video:

Note: You have until August 28, 2026 to update your SSO integration.  

For Organizations Using Solsta-Provided Login

If your organization uses a Solsta-provided login (Auth0), we will migrate all your users to Cognito during our maintenance window. This will result in all existing users receiving a temporary password via email that can be used to log in to the new system. Users will be prompted to set new passwords during the initial login to the new client.  

  • Please check your spam/junk folders on June 26 if the temporary password email is not in your inbox. The email will come from noreply@solsta.io.  
  • The email subject line will be “Your Solsta account has been created”
  • If you’d like to prevent inactive or former users from receiving these temporary password emails, please remove them from your organization before June 26
  • Temporary passwords will be valid until changed on first login. If a user cannot locate the email or access their temporary password, please contact Solsta Support.

Migration Questions

Will there be downtime during the migration?

Yes. There will be a four-hour window where we will be updating our backend systems from 6:00 PM to 10:00 PM PDT on June 26, 2026. During this time, new build deployments (uploads) and installs/updates will be impacted.  


What’s going to happen to my existing user or team roles?

All current users, teams, roles and permissions for your organization will be migrated during our maintenance window.  


Will my existing SSO group to Solsta team integrations continue working?  

Yes. Whether you update your SSO integration to work directly with Cognito or stay on Auth0 during the transition, your groups will continue to be associated with your Solsta teams.  


Will the migration impact my deployments or CI/CD integrations?  

Not immediately. Existing M2M credentials will continue to work with your existing deployment tools in your CI/CD pipeline. After this migration, we recommend transitioning to the new deployment executables or plug-ins, as well as a new set of credentials created in Solsta 2.1.  


Will the existing installations on my devices remain?  

Yes. User installations will be migrated as long as the login and device remain consistent.  


Can we test the Cognito SSO integration before the cutover date?

Yes. To test your updated SSO integration:  

  1. Add the new redirect URI to your Solsta application within your SSO system
  1. Notify us via a support ticket
  1. Receive a unique login URL  
  1. Test your new SSO integration in a web browser


Will my existing caching server redirects be migrated?

Yes. All organization-level settings, including caching server redirects, will be transitioned to the new system and visible within the new client.  


Will my existing throttling rules be migrated?

Yes. All organization-level settings, including throttling rules, will be transitioned to the new system and visible within the new client.


Will users be logged out after the migration?  

Yes. After users update to the Solsta Desktop Client version 2.1 or Solsta CLI version 8.0.46, they will need to log in via our updated authentication flow.  


Will existing SSO integrations (via Auth0) remain available for a transition period? When will it be fully retired?

Yes. Existing SSO integrations via Auth0 and M2M credentials will be available until August 28, 2026.


What happens if there is an issue during the maintenance window? How can I be notified of updates?  

If we identify an issue that may extend the maintenance window or affect user access, we will provide updates through https://solsta.statuspage.io. Please subscribe to receive notifications on our progress.  


Why is Solsta making this change? What does this mean for Solsta’s security posture?

Solsta is migrating authentication services to improve security, reliability, and integration with our authorization model. The new authentication service enables support for passkeys, account takeover protection, AWS WAF integration, and improved permission management capabilities.


Will customer IdP credentials or secrets be stored differently?

Customer IdP credentials and secrets will continue to be handled securely. Customers using SSO will only need to add the new redirect URI; this change does not require a new IdP integration secret. If any customer-specific IdP configuration changes are required, Solsta Support will coordinate those directly with your organization.

Support Contact and Deadlines

Deadlines:  

  • June 26, 2026 6PM to 10PM PDT – Migrate backend services and clients to use Cognito
  • Aug 28, 2026 – Retire existing, Auth0-based M2M credentials