Describe the bug
Currently all client APIs are failing scope authorization despite having the "all:all:all" scope. This is occurring because we are using NewCasbinStringAuthorization instead of NewCasbinScopeAuthorization for the scope authorization on the client auth handlers.
To Reproduce
Steps to reproduce the behavior:
Make request to any client API with valid user token
Receive 403 error
Expected behavior
The client API requests should succeed if a valid user token is provided.
Describe the bug Currently all client APIs are failing scope authorization despite having the "all:all:all" scope. This is occurring because we are using
NewCasbinStringAuthorization
instead ofNewCasbinScopeAuthorization
for the scope authorization on the client auth handlers.To Reproduce Steps to reproduce the behavior:
Expected behavior The client API requests should succeed if a valid user token is provided.