Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,654
Community Members
 
Community Events
176
Community Groups

Atlassian Access & Cloud Premium

Check out this short video to learn about using Atlassian access with Jira Software & Confluence Premium:

Learn more about Confluence Premium here, and watch the next video in the series - How to use bulk archive in Confluence Premium

2 comments

John Funk Community Leader Nov 30, 2020

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? 

Like # people like this

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!


Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events