#1809 Document that SSSD domains should only be named using ASCII characters
Closed: Fixed None Opened 11 years ago by jhrozek.

The Kerberos include files only accept alpha-numeric chars, dashes and underscores are allowed in krb5 include directory. The SSSD currently substitutes underscore for any characters outside the scope, but this is prone to conflicts.

We might want to use something like ToASCII defined in RFC3490:
http://tools.ietf.org/html/rfc3490#page-10


Turn to man page note.

milestone: NEEDS_TRIAGE => SSSD 1.10 beta
rhbz: => todo

Fields changed

summary: Provide a safer method to encode UTF8 characters for the Kerberos include files => Document that SSSD domains should only be named using ASCII characters

Fields changed

owner: somebody => jhrozek
patch: 0 => 1
review: => 0
status: new => assigned

resolution: => fixed
status: assigned => closed

Fields changed

changelog: =>
rhbz: todo => 0

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.10 beta

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/2851

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