You want to migrate from the deprecated Identity Federation for AWS 1.x to its successor Identity Federation for AWS (Jira) 2.x to gain new features and improvements:
Step-by-step guide
Unfortunately there is no upgrade path from Identity Federation for AWS 1.x to its successor Identity Federation for AWS (Jira) 2.x for technical reasons outside of our control. To ease the migration, you can start using versions 1.x and 2.x for Jira side by side, as they are entirely independent apps (usability flaws apply though, see 3. below).
1. Install Identity Federation for AWS (Jira) 2.x.
2. Start creating connectors in Identity Federation for AWS (Jira) 2.x exclusively (see 3. for how to differentiate the two apps).
3. Replace existing connectors from Identity from Identity Federation for AWS 1.x with the functionally identical (though possible extended) connectors in Identity Federation for AWS (Jira) 2.x. Both Both expose identical user interface entries for menus and links though and you need to take care differentiating those as follows:
Hoovering over some UI elements (e.g. a menu item or a link) exposes the link targets, which differ regarding the app key and the app connector id format (thew new app uses GUIDs rather than integers), e.g.:
App Name | Link Target |
|---|---|
https://<host>/<context>/plugins/servlet/identity-federation-aws/aws-console-login/1 | |
https://<host>/<context>/plugins/servlet/identity-federation-for-aws/aws-console-login/fd3f4265-1ba1-4045-92d4-142a1e271c7d |
The apps expose different naming and versioning:
App Name | App Versions | App Key | REST API |
|---|---|---|---|
1.x | net.utoolity.atlassian.identity-federation-aws | ||
2.x | net.utoolity.atlassian.jira.identity-federation-for-aws-jira |
4. Disable/Uninstall Identity Federation for AWS 1.x once all desired connectors are provided by Identity Federation for AWS (Jira) 2.x.
| Info |
|---|
Providing an explicit (automated) migration option is not out of the question, but a disproportionate amount of work for us right now - please get in touch, if your use case requires a migration option regardless, we are willing to discuss this on a case by case basis. |
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
|