Pronghorn JSON

BREAKING CHANGE

The following is a breaking change in pronghorn.json for the 2023.1 release.

Protection Key Update (2023.10

In an earlier release, IAP had modified the protection key in pronghorn.json to override the default authorization utilizing roles by adding support for both public or trusted methods. See Public and Trusted Methods for additional detail.

When overriding the protection key in 2023.1, you must NOT have any roles defined on the method. Those roles will no longer be useful, and it will only add confusion around which authorization scheme is required. By default, role-based authorization is used if the protection property is not set.

What should I do?

For any custom applications that contain routes which set the “protection” property to trusted or public, the “roles” property must be empty. Verify there are no defined roles on the protection property in the pronghorn.json of your custom app.