Issue Summary

Offline user Impersonated calls from a Forge Remote fail with 401 unauthorized if the user changes their password. Even if we get a new token using forge_remote_offlineUserAuthToken mutation, the new token also fails.

Steps to Reproduce

• Get a token for a user using forge_remote_offlineUserAuthToken mutation
• Use the token to make a REST call (i.e /rest/api/3/search/jql)
• change the password of the user
• make the same call using the same token - it fails with 401
• Get a new token using forge_remote_offlineUserAuthToken mutation
• make the same call using the new token - it fails with 401

Expected Results

API call should be successful.

Actual Results

API call fails with {}401 Unauthorized{} error.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available