I am completing work on implementing user impersonation through the oauth2 bearer token.
My question is regarding the sub key in JWT tokens that contains the userkey. I understand that we will no longer be able to impersonate users through the sub field in the JWT claim on 8/1/2017. However, will Atlassian still continue to provide the userkey in the sub field of the claim when making requests to the add-on. We currently use the sub to resolve the user key. I haven’t found anything in the documentation that says this will change, so we are assuming that the userkey will still be available in the token claim. However, I would really like to be sure of this. Please confirm if this is accurate.