Learn more about these different git repos.
Other Git URLs
We may want to enhance our GPO documentation and make it step-by-step, to make sure users can do tasks like allowing SSH from AD.
It might be part of wiki Active Directory integration or at least linked from this wiki.
Document that only UTF8 is supported in GPO ini files. "ISO-8859-x" and others cannot be parsed by libini_config.
It was discussed on IRC #sssd with bartoua (08 Dec 2015).
example non-utf8 GPO file GPT.INI
ini_config supports UTF8, UTF16 and UTF32 both BE & LE. AFAIU the file needs to have BOM indicator that shows the encoding. It seems that using ISO-8859-x is not valid.
Replying to [comment:2 dpal]:
ini_config supports UTF8, UTF16 and UTF32 both BE & LE. AFAIU the file needs to have BOM indicator that shows the encoding. It seems that using ISO-8859-x is not valid. That's true. Bt we can recommend to mainly use UTF8
One question -- is this an issue with this setup in particular or with any kind of GPOs on localized Windows servers? If it's the latter, then I think we should support that..
Replying to [comment:4 jhrozek]:
One question -- is this an issue with this setup in particular or with any kind of GPOs on localized Windows servers? If it's the latter, then I think we should support that.. I don't know. It was the first reporter. But he mentioned it works with English text in file on another machine.
It would be difficult to guess character encoding from file. Therefore we should just recommend to use UTF-8. If there will be many users which will require other encoding then we can reconsider the decision later.
As agreed, we might just want to point out to MSFT documentation, not write the docs ourselves.
milestone: NEEDS_TRIAGE => SSSD 1.13.4 priority: major => minor
Fields changed
rhbz: => 0
Hmm, this is an easy task, but we forgot about it a bit in 1.13.4. Let's do it in 1.13.5
milestone: SSSD 1.13.4 => SSSD 1.13.5
Moving to triage, because nothing happened with the ticket for half a year, so 1.13 is probably not the best milestone.
milestone: SSSD 1.13.5 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => Wiki Updates
Metadata Update from @lslebodn: - Issue set to the milestone: Wiki Updates
Metadata Update from @jhrozek: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Moved to https://pagure.io/SSSD/docs/issue/34 as a link
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
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/3935
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.