Hello Pavel,
Nice work on this guide, I think it will be very useful!
I used the Fork and Edit button to add some information and make some minor changes.
Fork and Edit
https://pagure.io/fork/jstephen/SSSD/docs/c/f24625499ccebc47a01067cfd5a8411cbdfd2e4e?branch=backend
Besides the changes above, some other thoughts were
Could it be worth mentioning that the authentication/access control SSSD handlers are only called if the PAM configuration is correct and pam_sss is reached traversing the PAM stack.
Should there be some mention of the krb5_child.log in the authentication section? I think this probably depends on how generic this backend guide is intended to be(non-AD, non-IPA specific)
Do you think debug_level 9 logs should be requested at least in the Asking for help section?
@pbrezina could you please rebase the patches and include links to the new page from the generic troubleshooting guide that is now merged?
Thank you for rebasing the patch, but why did you add a new troubleshooting section and not added the new document to the existing user section? I would be OK with a troubleshooting sub-section under 'users' but the main idea I had was to keep the pages most people need (and most people are users looking for troubleshooting) at the top in the users section so it's easily visible.
I would also propose to get bidirectional links between this page and the generic troubleshooting guide.
Did I rebase the patch? I don't remember :-) I can put it into users directory, I don't mind. Also Justin's idea are good, I will incorporate them into the document. Thank you.
rebased
I added Justin's comments and move it to users/troubleshooting.
@jstephen I assume that you are fine with current version or can you fine anything else after longer period :-) ?
Looks good to me, thanks!
Commit d534112f fixes this pull-request
Pull-Request has been merged by pbrezina@redhat.com