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

How do you setup unverified in Access and SSO or SCIM

We need to add contributors across over 20 different domains. These are outside users from outside companies. How do setup SSO or SCIM if you have no ability to verify their domain?

1 answer

0 votes
Jayant Suneja
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 16, 2021

Hi,

Though it's not possible to enable SSO without verifying the domain, we have released a new feature that allows you to provision users outside your verified domain to Atlassian via SCIM. Please refer:

Provision-users-from-outside-your-verified-domain-to-atlassian-products 

Here is the scope of this new feature:

  • External accounts in your IDP can be added to the site via provisioning
  • External accounts in your IDP can be added as members to the provisioned groups

What's not in the scope of this feature:

  • We will not sync attributes from the IDP to the external accounts in Atlassian (i.e., Display Name, Job Title, email address, etc..).
  • When an external account is deactivated on your IDP, the Atlassian Account will not be deactivated. Instead, the accounts will be removed from the provisioned groups.
    • If the external user is part of any local group on the site, those need to be removed manually from the site administration of mogroup.atlassian.net.
    • The remaining account on the site (without any group membership) will need to be also removed manually.
  • If a new provisioned external account is not yet known to Atlassian, the end-user will still need to complete the account creation by verifying their email address mailbox.

Regards,
Jayant

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events