Getting 401 on Connect App API calls


Since last week we are getting 401 responses on all API calls made to a Jira instance that we test with.

We are trying to verify the payload sent back on the install lifecycle but is there any recent changes that would cause the client id or secret to have changed?

Please advise if there is anything that has changed?

Thank you

Connect recently moved away from a shared secret model to a per-installation shared-secret model. Here’s a related thread with more info:

1 Like

@danielwester thank you very much for that response. That was the issue … Also, I have posted an update as I would like to ensure we are going through the correct process and managing our private custom conneect app properly - Atlassian Connect App installation lifecycle updates or checks

Thank you