Hi,
Can we set up Okta SSO for testing purposes in the free tier of the self-hosted version 3.75.3? In the interface under Settings > SSO, I only see Google SSO available.
Regards,
Baktash Salehi
Hey @baktash.salehi! Thanks for reaching out.
As an org on the free tier, you don't have the ability to configure SSO access with a custom IDP like Okta. I can look into getting you an Enterprise trial, though, if you are really considering an upgrade!
Hi @Darren, Thank you for your response.
We are currently using a Retool enterprise license in our production environment, which is actively utilized by our colleagues and connected to Okta SSO via the organization’s server. We plan to configure the Okta authorization server feature with our Retool instance and would like to test it before applying it to the production environment. We would appreciate it if you could provide us with an enterprise trial for this purpose.
Please let me know if further information is needed.
1 Like
Ah understood! In that case, you can just replace the key that you're currently using with your org's existing Enterprise key in order to unlock all features on your testing instance. It's not always made clear, but the same key can be used for multiple deployments.
@Darren I’m wondering if using key for multiple deployments incurs any additional charges. If so, could you please provide an estimate?
There is no additional cost specifically associated with deploying additional instances. The things you do pay for - users, workflow runs, etc. - are shared across all deployed instances, though, so it is theoretically possible to use those resources faster. And you'd end up paying a bit more for the necessary infrastructure.
Thank you for the quick response.
1 Like
Hello @Darren,
I have used our enterprise license to set up a new instance. However, the new instance, despite having the enterprise license, is still prompting for an upgrade. I have attached a screenshot for reference. Is there any additional process or configuration needed?
For context, Initially, I configured this instance with a free license and later switched it to the enterprise license. I have added the license to the docker.env file.
Regards,
Baktash Salehi
Have you cycled your containers since modifying docker.env? Containers are meant to be immutable processes, meaning changes won't be automatically detected.
1 Like
Thank you, @Darren; this worked!
1 Like
@Darren, currently both the development and production environments are using the same license, and I hope this won't cause any issues or challenges in production later! as currently both are working as expected.
Nope! That's an intended use case and perfectly expected. 
1 Like