-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Doc] kerberos debug instructions #15779
Conversation
Co-authored-by: João Duarte <[email protected]>
Co-authored-by: João Duarte <[email protected]>
Co-authored-by: João Duarte <[email protected]>
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.
Left some comments inline for your consideration--one wrt formatting and one wrt next steps. Please let me know if you'd like to discuss or iterate.
@kaisecheng , thanks for adding this! I added myself as an assignee fso that we can track this effort in |
Co-authored-by: Karen Metts <[email protected]>
@karenzone Thanks for the review. I have accepted the suggestion and made a small change. |
@@ -173,7 +173,7 @@ You can set up your machine to help you troubleshoot authentication failures in | |||
+ | |||
[source,txt] | |||
----- | |||
`-Dsun.security.krb5.debug=true` to `jvm.options` | |||
-Dsun.security.krb5.debug=true |
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.
Thanks for catching and fixing this, @kaisecheng :-D
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.
I left one more comment about aligning the section heading with content in the topic. Please consider it. Either way, LGTM. Thanks for adding this info!
|
||
NOTE: Logging entries for Kerberos are NOT sent through Log4j but go directly to the console. |
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.
The heading implies that we're giving steps for debugging, but we're only helping the user set up debugging. Can we provide more information, even something as simple as reworking the note to say, "Go to the console to see your log entries"?
Another approach would be to change the heading to "Setting up debugging for Kerberos SASL" to set expectations for what's in the topic.
add instructions to enable kerberos debug log
Fixes: #15802