search

robsontenorio / laravel-keycloak-guard

🔑 Simple Keycloak Guard for Laravel
MIT License
434 stars 141 forks source link

Avoid resource_access control #61

Closed enrico-bellanti closed 2 years ago

enrico-bellanti commented 2 years ago

I'd like to avoid the resource_access control, because i would like to manage directly from my backend, i connot find any solution around if not delete directly the control in the Guard. It would be great have a configuration at Keycloak.init(), but i cannot find it. Any solutions?

kabircse commented 2 years ago

I'd like to avoid the resource_access control, because i would like to manage directly from my backend, i connot find any solution around if not delete directly the control in the Guard. It would be great have a configuration at Keycloak.init(), but i cannot find it. Any solutions?

I am also facing this error in api call(postman) ?

kabircse commented 2 years ago

I'd like to avoid the resource_access control, because i would like to manage directly from my backend, i connot find any solution around if not delete directly the control in the Guard. It would be great have a configuration at Keycloak.init(), but i cannot find it. Any solutions?

I am also facing this error in api call(postman) ?

I solved this issue. I have to create a user role under the client. After then I have to put these roles name in keycloak.php as resources name.