| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
General FAQ
How do I set up Identity Federation for AWS?
Please refer to the Installation and Upgrade Guide.
Which Atlassian products are currently supported by Identity Federation for AWS?
Identity Federation for AWS aims to be a cross product solution, however, we've focused on JIRA to get things started (please refer to the Compatibility Notes for details) - please get in touch with us, if you are interested in support for other Atlassian products, we are eager to learn more about your use case and adjusting our respective roadmap accordingly (see below for a notable special case though).
Will Identity Federation for AWS be available for Atlassian Crowd?
Identity Federation for AWS aims to be a cross product solution and Atlassian Crowd would be the most obvious target product for Enterprise deployments. The add-on could work within Crowd in principle, however Crowd currently lacks the Universal Plugin Manager (UPM) and support for selling Crowd add-ons via the Atlassian Marketplace in turn - this issue is tracked by Atlassian in Support the Universal Plugin Manager in Crowd (CWD-3157), so please add your vote there to increase the priority and also get in touch with us to discuss alternatives.
Security FAQ
How are my persisted long-term AWS security credentials secured against unauthorized usage?
The persisted long-term AWS security credentials (comprised of an Access Key Id and an a Secret Access Key) are stored in the database encrypted with a 128-bit Advanced Encryption Standard (AES) private secret key, which is stored on the file system and unique per application instance (e.g. JIRA installation). This means you can loose either your database or your file system without compromising your AWS accounts right away.