Before, any role requirement set in a controller at class-level didn't have any effect. This PR fixed this.
This PR is about setting the roles properly for the affected controllers. Looking through the controllers, I only found the chirpstack gateway endpoint to be affected. If a user with only read permissions tried to access the page before, they would get 401. The changes here address this.
The current implementation of roles has the role guard set on each endpoint take priority. I.e. if the gateway controller has @Write on a class-level but @Read on a POST-endpoint (say, create()), then only @Read is evaluated.
Before, any role requirement set in a controller at class-level didn't have any effect. This PR fixed this. This PR is about setting the roles properly for the affected controllers. Looking through the controllers, I only found the chirpstack gateway endpoint to be affected. If a user with only read permissions tried to access the page before, they would get 401. The changes here address this.
The current implementation of roles has the role guard set on each endpoint take priority. I.e. if the gateway controller has
@Writeon a class-level but@Readon a POST-endpoint (say,create()), then only@Readis evaluated.