-
Suggestion
-
Resolution: Unresolved
-
None
-
64
-
Problem
Currently, Atlassian Access applies a single configuration to an Identity Provider(IdP) for non-enterprise customers.
Enterprise customers received the feature to have multiple IDPs configured. But non-enterprise customers have a serious problem when they are looking to migrate from one IDP to another as they need to wipe out their current working IDP configuration to configure the new one.
This poses a problem for organizations as they need to take extra caution before proceeding, including accounting for prolonged user downtime, more communications to be sent information about the changes, and also more lengthy change windows.
Solution
Provide a way for non-enterprise customers to enable multiple IDPs temporarily, allowing them to test the configuration of the new IDP without having to delete the IDP that is already working.
On August 2023, a new feature was released by the development team to allow non-enterprise Access customers to create a second IdP without the need for an Enterprise Subscription or Enterprise Override.
Two new operations have been made available for Support engineers that will enable an org to create the second IdP (directory) for 30 days, and updated to up to 60 days.
Please note that this feature is still in the experimental phase, but customers that want to enable this feature to temporarily have a second IdP configured can raise a support ticket for Atlassian requesting it.