Versions Compared

Old Version 5

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

compared with

New Version 6

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Adjusted regarding dedicated add-ons per application.

31 July 2014

Tip
iconfalse
Div
stylepadding-bottom:0.8em
The Utoolity team is pleased to present Identity Federation for AWS 2.0 – this major release adds support for Atlassian Bamboo, adds system scoped AWS credentials for elevated API usage without an active user session, and upgrades the API to version v2 to support secure configuration migration across instances/installations.
Section
Column

Highlights of this release:

Table of Contents
minLevel3
excludeRelease [1-9]\.[0-9]\.[1-9]+

Column

 

Column

Updates for this release:

Table of Contents
minLevel3
includeRelease [1-9]\.[0-9]\.[1-9]+

...

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1

Support for Atlassian Bamboo

Use Identity Federation for AWS in Atlassian Bamboo to gain the following benefits:

Include Page
_CrossProductSupportNote
_CrossProductSupportNote

Info
titleDedicated Add-ons per Application

Bamboo and JIRA are each supported via a new dedicated add-on per Atlassian application due to Marketplace restrictions for cross-product add-ons:

  • the former JIRA only add-on will be archived, but can technically be used in parallel (minor usability issues apply)
  • the add-ons operate independent right now, i.e. credentials need to be managed separately for each and duplicated if desired - cross-product usage via application links is on our mid-term roadmap
Panel
borderColor#F3F3F3
bgColor#FFFFFF

System scoped AWS credentials

An AWS connector can now be denoted as System scoped and then used from elevated code (e.g. within another add-on) without an active user session to allow usage within Atlassian Bamboo's Tasks for example, as facilitated by Tasks for AWS.

...