Currently the ml-forecast service expects read:admin write:admin roles (#3)
These are quite broad and don't indicate that they provide access to this service, therefore ideally the service has more specific roles such as write:config-forecast read:config-forecast or something similar.
Investigate this particular issue and detail a method on how to implement more granular and service-specific roles.
Ideally this implementation allows annotation similar to JAX-RS e.g. RolesAllowed this should be fairly straight forward using python decorators. This can also then be used to automatically exclude paths from the middleware that are missing the appropriate annotation.
Currently the ml-forecast service expects
read:adminwrite:adminroles (#3)These are quite broad and don't indicate that they provide access to this service, therefore ideally the service has more specific roles such as
write:config-forecastread:config-forecastor something similar.Investigate this particular issue and detail a method on how to implement more granular and service-specific roles.
Ideally this implementation allows annotation similar to JAX-RS e.g.
RolesAllowedthis should be fairly straight forward using python decorators. This can also then be used to automatically exclude paths from the middleware that are missing the appropriate annotation.