nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Staged user accounts in IDP does not create a user account in Atlassian Admin console

faiz.jumari

Hello,

Atlassian access is managed by JumpCloud IDP.
When a new user is added to JC, they will be in Staged status.

We have a dynamic group called Atlassian-Portal whose attributes are:
When User State equals Activated or Staged

This means any users that gets added to JC with the status Staged or Active, they will automatically be added to this group.

This group will give them Customer access to Jira Service Management

However it seems that their Atlassian account will only be created in Atlassian Admin console, if their Jumpcloud account is Active.

We do not want user's JC account to be Active until their actual start day. So until then, their account will be in Staged status.

Is there a way for their Atlassian account to be created even when they are in Staged status in JC?

If anyone has experienced this before, your resolution/ workaround will be highly appreciated.

Accepted answers

Marc -Devoteam-

Hi @faiz.jumari

I don't think this an Atlassian related question, but a Jumpcloud related question. As I suspect this is not a specific topic to Atlassian applications.

I would reach out to them and as why new accounts setup as suspended are not synced, when JC is connected as the IDP for SSO.

You can also check this Atlassian doc: understand-user-provisioning and this doc from Jumpcloud: integrate-with-Atlassian-cloud

I do suspect on reading the Atlassian doc that the integration only looks at active and inactive and that Staged is recognised as inactive and there not be synced, unless set active in Jumpcloud.

All comments

Marc -Devoteam-

Hi @faiz.jumari

I don't think this an Atlassian related question, but a Jumpcloud related question. As I suspect this is not a specific topic to Atlassian applications.

I would reach out to them and as why new accounts setup as suspended are not synced, when JC is connected as the IDP for SSO.

You can also check this Atlassian doc: understand-user-provisioning and this doc from Jumpcloud: integrate-with-Atlassian-cloud

I do suspect on reading the Atlassian doc that the integration only looks at active and inactive and that Staged is recognised as inactive and there not be synced, unless set active in Jumpcloud.

faiz.jumari

Thanks for the input @Marc -Devoteam-
I've raised a ticket with JC as well.
Will post here for any updates.

faiz.jumari

Yeap, so they replied saying that its gonna be a feature update for this. So indeed, it is from their side.

In the meantime, my team utilized a workflow tool to create user's account in Atlassian with their exact email address and with the needed permission.

So when new user onboard and JC is Active, it will override the created Atlassian account and it will become a JC managed account. Solving our problem for now.

Thanks for taking the time to respond @Marc -Devoteam- ! Appreciate it!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management