-
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
feat(config-api): agama deployment path param change and client authorization #4147
Conversation
[jans-cli] Kudos, SonarCloud Quality Gate passed! |
[Fido2 API] Kudos, SonarCloud Quality Gate passed! |
[Jans authentication server parent] Kudos, SonarCloud Quality Gate passed! |
[jans-config-api-parent] SonarCloud Quality Gate failed. |
if (logger.isDebugEnabled()) { | ||
logger.debug("User search param - limit:{}, pattern:{}, startIndex:{}, sortBy:{}, sortOrder:{}", | ||
if (logger.isInfoEnabled()) { | ||
logger.info("User search param - limit:{}, pattern:{}, startIndex:{}, sortBy:{}, sortOrder:{}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pujavs We are flipping logging level back on forth all the time. I guess we should decide what level do we use to log request/response and simply stick to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies, there are issues cropping up for user mgmt for different persistence type and needed the logs to appear for these. Since debug is not the default log level and these logs were not appearing in logs when reported.
Prepare
Description
Target issue
closes #4048
Implementation Details
Test and Document the changes