Details about cause of the IllegalArgumentException: User doesn’t have permissions

If you see anything like the exception below, this page could be helpful.

The cause of the exception is that the user who accesses the app configuration on the repository level does not have permission to read it.

Another possible scenario is when Jenkins or an automation script creates a repository-level configuration rule and uses a user who can only read the Bitbucket repository, but not an admin.

To avoid this, the global admin can enable a global setting “Allow repository readers to read repository configurations“. This will permit users who are only repository readers and not repository owners/admins to read the Bitbucket Post Webhook configurations for the repository

Updated: