-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"MUST Secure Endpoints" violation using Bearer Auth #1251
Comments
@cberg-zalando thank you for creating the ticket. There is a bug in one of the checks. The mitigation strategy for now is to use |
I also learned that the definition of scopes before OpenAPI 3.1.0 is actually a violation, so the ideal situation would be if zally would support the latest OpenAPI version as outlined already in #1230. |
@vadeg I actually fixed the first part in #1247. However, I overlooked, that OpenAPI |
@tkrop thanks. I am fixing this one already. |
Even with the implementation of #1247, our builds still fails due to violating
MUST Secure Endpoints
endpoints saying e.g.The scope 'BearerAuth/wrapping-eligibility.read' is not specified in the clientCredentials flow of the OAuth2 security definition
(see https://sunrise.zalando.net/cdp/ghe/broadway/wrapping-eligibility/l-2fdr94fskn5ymahu4h82yvirbc/steps/0/logs for details).As the RESTful API guidelines do not mention anything about specifying scope information, either the check needs to be adjusted or something is missing in the guidelines.
The text was updated successfully, but these errors were encountered: