-
Notifications
You must be signed in to change notification settings - Fork 75
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(jans-config-api): incorrect server response for missing agama resources #2924
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
Component affected by issue or PR
kind-bug
Issue or PR is a bug in existing functionality
labels
Nov 8, 2022
@moabu, this is on jenkins build env |
let me try again |
@pujavs the issue still seems to exist.This is with the latest on MySQL. |
5 tasks
handled Exception , fix via PR 3028 |
Now this is returning a 200 code instead of 404 |
5 tasks
Fixed and tested on mysql env |
Tests and is working as expected |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
comp-jans-config-api
Component affected by issue or PR
kind-bug
Issue or PR is a bug in existing functionality
When trying to fetch an agama flow that does not exist, instead of a 404 response, the server return 500. This was introduced with the latest deployment.
The request is run against
/jans-config-api/api/v1/agama/QNAME
where QNAME is the name of a flow that is not defined in the system.The text was updated successfully, but these errors were encountered: