lakshya8066 opened a new pull request, #10763: URL: https://github.com/apache/apisix/pull/10763
### Description <!-- Please include a summary of the change and which issue is fixed. --> <!-- Please also include relevant motivation and context. --> In the authz_keycloack plugin, when we set `lazy_load_paths` as true and do not provide `resource_registration_endpoint` either in the plugin config or in the discovery doc we get a 500 error code. This error code comes from here https://github.com/apache/apisix/blob/ab67b095bf7200274b37af5c589fc093858d98e8/apisix/plugins/authz-keycloak.lua#L580 when we try to get the length of `permission` because an integer value, 503, is passed to it from here https://github.com/apache/apisix/blob/ab67b095bf7200274b37af5c589fc093858d98e8/apisix/plugins/authz-keycloak.lua#L506 This PR changes the return value of `permission` to `nil`. This will now return error 503 when this check runs: https://github.com/apache/apisix/blob/ab67b095bf7200274b37af5c589fc093858d98e8/apisix/plugins/authz-keycloak.lua#L569 Fixes #10708 ### Checklist - [x] I have explained the need for this PR and the problem it solves - [x] I have explained the changes or the new features added to this PR - [x] I have added tests corresponding to this change - [ ] I have updated the documentation to reflect this change - [ ] I have verified that this change is backward compatible (If not, please discuss on the [APISIX mailing list](https://github.com/apache/apisix/tree/master#community) first) <!-- Note 1. Mark the PR as draft until it's ready to be reviewed. 2. Always add/update tests for any changes unless you have a good reason. 3. Always update the documentation to reflect the changes made in the PR. 4. Make a new commit to resolve conversations instead of `push -f`. 5. To resolve merge conflicts, merge master instead of rebasing. 6. Use "request review" to notify the reviewer after making changes. 7. Only a reviewer can mark a conversation as resolved. --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
