Enable SSO or AD for JIRA integrations Merged

Our security policies don't allow storing credentials on servers we don't control. To get the JIRA integration to work we need to create a local JIRA admin user account which we then use with the AHA integration setup. Since we have 20-30 products in AHA mapping to various JIRA projects we now have to use that admin account for each setup.
A related problem is mapping AHA user names to JIRA user names. We use AD integration to login to JIRA which than uses the AD username to tag JIRA records modified by that user. With the current integration AHA attempts to map the aha user to the JIRA user but when that fails it tags modified records with the local admin user. We now lost the ability to track down who actually made the record changes. The attached doc has more details.