Hi @Jessica Taylor - We are wanting to test out Atlassian Access against a Sandbox to make sure we understand the functionality and process to set it up correctly. I have created a sandbox against our premium instance, but our IT group is nervous that it will affect our production instance of Jira. Or that it will adversely affect our Okta settings if we connect to another sandbox instance and then switch to our production instance.
How can we best test this out to ensure integrity of all of the systems/tools with easy rollback if something doesn't go right?
Atlassian Team members are employees working across the company in a wide variety of roles.
December 1, 2020 edited
Hey @John Funk - Thanks for your question. It's not possible to test Access features within a Cloud Sandbox because access is configured at the org level and sandboxes are sites.
You can test Access features using Authentication Policies. (See the “Testing your authentication settings” section.) The caveat here is only currently enabled for a subset of current customers. If your team falls into this category, you can use authentication policies to set up SSO for a limited number of users first. The Access team is bringing this to all customers early next year.
An alternate solution would be to create a separate test org, verify a different domain, and test it out. If you'd like to be added to a list of customers who want quicker access to auth policies, let me know!
2 comments