I have hit the same exact issue.
True SSO integration into JIRA does not maintain a user password outside of that system (nor does it allow the user or the admin for that matter, to change a user’s password). As such, the only workaround I’ve found thus far is to create a user that exists outside of the SSO solution. This presents a number of issues:
- Any user configured this way is bypassing any security put in place by the SSO solution.
- It requires every single user that needs to file bugs (using the JIRA plugin) to have one of these system-circumventing configurations to accurately show who is logging a bug (upon test failure). A single shared account would show that all filed issues were reported by that single user.
As for retrieving the the API credentials, from what I can tell, it’s a temporary token that’s issued (for that session). Timeouts for this token vary, likely from instance to instance depending on the configuration, but everything I’ve tried has not allowed a means of statically setting a value that’s retained and able to be used consistently.
@dgrange-gp - I too am still seeking a legitimate configuration that will allow us to properly integrate TestRail and JIRA (With OKTA SSO). Should I find anything prior to your doing so, I’ll be sure to post to this thread.