#496 review sssd-krb5 man page for accuracy
Closed: Fixed None Opened 13 years ago by obriend.

After some discussion with sgallagh:
"it's probably a good idea to open a ticket to have engineering go through that for accuracy, and then have you wordsmith it."

Please indicate:

  1. Whether each option is mandatory or not

  2. Default values for any options that have them


Fields changed

component: SSSD => Documentation
milestone: NEEDS_TRIAGE => SSSD 1.2.1
owner: jhrozek@redhat.com => jhrozek
priority: major => critical

I have reviewed the manpage and I think it looks mostly OK. The manpage lists all available options, those that are optional have a correct "Default" value

The krb5_realm option should indicate that it is mandatory with no default (until ticket #481 gets implemented). The krb5_kpasswd should probably say something like "Default: use KDC".

Would you like me to prepare a patch for these issues? Feel free to ping me on IRC if you have any additional questions..

status: new => assigned

Yes, please prepare a patch and if nobody has any additional comments from a technical perspective I'll look at it from a language/readability perspective. I can then extract anything needed and add it to the user doc.

thanks

Could we elaborate on the situations that require the use of the 'krb5_changepw_principal' setting, and what the proper value is in those situations? I'm drawing a blank there.

Fields changed

cc: => nalin

When I wrote the password change part of the Kerberos provider is was reluctant to use a hard coded value of 'kadmin/changepw' because I wasn't sure if there are environments which allow to change this value. If you think this option is useless would you mind open a new bug to remove this option?

Replying to [comment:6 sbose]:

When I wrote the password change part of the Kerberos provider is was reluctant to use a hard coded value of 'kadmin/changepw' because I wasn't sure if there are environments which allow to change this value. If you think this option is useless would you mind open a new bug to remove this option?

Sure. #531.

Fixed in 37f3536

fixedin: => 1.2.1
resolution: => fixed
status: assigned => closed

Fields changed

doc: 1 => 0

Fields changed

rhbz: => 0

Metadata Update from @obriend:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.2.1

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1538

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata