How to use an impersonating Application Link with Bitbucket's Access Key feature?

Dear Community,

I am using impersonating application links between Bitbucket and Jira to implement repository hooks in my app (some logic is run inside Jira). This works fine with regular authentication but with Bitbucket’s SSH Access Key feature, the authenticated username will become some auto generated hash-like value (e.g. “ba92b4d3cf8d743d”). Apparently, this user will not be existing in Jira, so the call through the impersonating application link will fail.

Is this the expected behaviour? If so, what is the recommendation for using impersonating app links with SSH Access Key authentication properly?

Thank you in advance,

1 Like