fix(jans-config-api): Fetching a non-existing trust relationship results in an empty body response and a 200 status #8162
Assignees
Labels
comp-jans-config-api
Component affected by issue or PR
kind-bug
Issue or PR is a bug in existing functionality
Comments
mo-auto
added
comp-jans-config-api
uprightech
changed the title
uprightech
added a commit
that referenced
this issue
Apr 1, 2024
…existing trust relationship #8162 Signed-off-by: Rolain Djeumen <[email protected]>
yuriyz
added a commit
that referenced
this issue
Apr 1, 2024
… returns a 200k empty response instead of a 404 Not Found #8162 (#8185) fi(jans-config-api): return 404 with body when trying to fetch a non-existing trust relationship #8162 Signed-off-by: Rolain Djeumen <[email protected]> Co-authored-by: YuriyZ <[email protected]>
yuriyz
added a commit
that referenced
this issue
Nov 7, 2024
… returns a 200k empty response instead of a 404 Not Found #8162 (#8185) fi(jans-config-api): return 404 with body when trying to fetch a non-existing trust relationship #8162 Signed-off-by: Rolain Djeumen <[email protected]> Co-authored-by: YuriyZ <[email protected]> Former-commit-id: c71ca5a
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Invoking the endpoint
/saml/trust-relationship/id/{tr_inum}results in a 200 OK response with an empty body if the specifiedtr_inumrefers to a non-existing trust relationship.Expected behavior
Invoking said endpoint should result in a 404 not found error with possibly an error object clearly indicating the trust relationship with said
inumcould not be found.The text was updated successfully, but these errors were encountered: