Atlassian connect app url/context doesn't have accountId

Question

I was trying to get accountId as I used to get user.key and user.id in jira cloud app. But I don't see accountId is passing in the request/context param. I tried to pass manually in atlassian connect descriptor but it didn't help: - ?accountId={user.accountId} - ?accountId={profileUser.accountId} How can I get accountId in my application either through request or any other way? Thanks
Masud

Masudur Rahman_959yyk · Answer

Thanks for your reply. Please look at the following url is being called from jira cloud issue details page using iframe to our app: https:///public/html/?projectId=10000&issueId=10000&user_id=&user_key=&tz=America/Los_Angeles&loc=en-US&xdm_e=https://.atlassian.net&xdm_c=channel-__viewissue-&cp=&xdm_deprecated_addon_key_do_not_use=&lic=none&cv=1.223.0&jwt= When I decode the jwt_string I get the following structure: { "sub": "", "qsh": "query_string_hash", "iss": "", "context": { "user": { "accountId": "", "displayName": "Display Name", "userKey": "", "username": "" } }, "exp": 1542131473, "iat": 1542130573 } If you look at the context property, it has accountId, so we can use this accountId from cloud app. But my question is this context param is an optional parameter as the following documentation says. https://developer.atlassian.com/cloud/jira/platform/understanding-jwt/ So If someone is trying to create JWT token and they don't pass context property is still valid JWT token and will pass authentication. But in that case we(app) won't have option to get accountId.

Earl McCutcheon · Answer

Hello,

Check out "Major changes to Jira Cloud REST APIs are coming to improve user privacy" it details the changes on the Key value under the section "Updates to APIs which accept user name or key as input"

Regards,
Earl