Skip to content
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

Fix authorization failure responses #137

Merged
merged 1 commit into from
Feb 15, 2024
Merged

Fix authorization failure responses #137

merged 1 commit into from
Feb 15, 2024

Conversation

hluk
Copy link
Member

@hluk hluk commented Feb 7, 2024

Messages and logging need to be improved for the new authenticated API to troubleshoot issues.

Failure to authorize a request with the service must be logged.

If permission is denied to post a data (or access an endpoint), 403 Forbidden status code must be returned (currently it is 401).

Failure to find user in LDAP should be send back to user (with 403 response including the test case name)

In case of LDAP errors, the service should return 502 status code (not 4XX).

Return JSON formatted responses consistently.

JIRA: RHELWF-10633

@hluk hluk requested a review from mvalik February 7, 2024 16:22
Messages and logging need to be improved for the new authenticated API
to troubleshoot issues.

Failure to authorize a request with the service must be logged.

If permission is denied to post a data (or access an endpoint), 403
Forbidden status code must be returned (currently it is 401).

Failure to find user in LDAP should be send back to user (with 403
response including the test case name)

In case of LDAP errors, the service should return 502 status code (not
4XX).

Return JSON formatted responses consistently.

JIRA: RHELWF-10633
@hluk hluk merged commit e25dba8 into develop Feb 15, 2024
11 checks passed
@hluk hluk deleted the fix-authorization branch February 19, 2024 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant