-
Suggestion
-
Resolution: Invalid
-
None
Thanks everyone for watching and commenting on this ticket.
As part of an initiative to consolidate feature requests/suggestions to gather centralized feedback, improving the popularity of the existing ones, we are closing this ticket as invalid as it does not rely on actions from Atlassian for its implementation.
Adding some context, the User provisioning relies on SCIM (System for Cross-domain Identity Management), to which we provided the SCIM REST APIs so that any Identity Provider can develop their solution to integrate their customers' userbase to Atlassian products. When the Identity Provider does not support this integration, it is likely because there are pending actions on their side. For such scenarios, we recommend reaching out to your Identity Provider channel for more details on their development cycle for this feature.
As always, thank you for the opportunity to improve our products, Feel free to bring additional feedback via existing suggestions!
João N.,
Atlassian Team
Issue Summary
Currently, Atlassian Access does not allow for User Provisioning when a customer is using ADFS as IdP. Especially in the DACH region, there are many Enterprise customers that are considering moving to the Cloud, but are using ADFS, which makes it a blocker for them.
Moving to a different provider that we do support, is not feasible for many customers in the short or medium term. Would it be possible to build a capability for Access to support User Provisioning via ADFS?
Expected Results
Being able to use User Provisioning with Atlassian Access and ADFS
Workaround
The current recommended workaround is to switch to a supported IdP, which is not feasible/a blocker for many Enterprise customers.
- is related to
-
- Closed
[ACCESS-1106] Allow for User Provisioning via ADFS
@Peter Leitner Do you have any update for the solution. Is it up for purchase now?
For all of those looking for a solution without scripting: We've developed one and it'll shortly be available for purchase. It technically works (we've already implemented it in customer environments) and we're currently in the process of license calculation. I know this is not an advertisement platform but since Atlassian won't come up with a connector themselves (as above), we decided to take action.
+1 on the desire to have that script. We've got a customer who desperately needs a solution to provision users from their local AD.
Hi, unfortunately we ran into several (not primarily technical) issues. I'm really sorry to have raised big expectations but at the time of writing this, we're unable to provide the solution to the public. :/