2009/6/3 Chris St. Pierre <stpierre@xxxxxxxxxxxxxxxx>
yes. fedora-idm-console does the same thing if you try to use that to manage policies.
I just ran into the same problem, actually, and found one of your oldOn Wed, 3 Jun 2009, tamarin p wrote:
Hi,
i apologize that i am revisiting this topic yet again but as we found out,
double quoted distinguished names are no longer possible in 1.2.0.
mailing list posts on it; I'd been meaning to ask about it on the
mailing list, so thanks for reminding me. :)
The ns-newpwpolicy.pl script creates double-quoted DNs, which are then
impossible (AFAICT) to modify. In other words, if you follow the
documented procedure for creating per-user or per-subtree password
policies, it doesn't work because the policy container is created with
a double-quoted DN.
yes. fedora-idm-console does the same thing if you try to use that to manage policies.
In addition to the OP's question, what's the Right Thing to do with
password policies? Will it work if I create the policy containers by
hand with the hex escape syntax? Or do I need to create them by hand
and populate them at creation time (since it's apparently still
possible to _add_ entries with double-quoted DNs, just not modify
them), and delete-and-recreate if I need to modify my policy?
I dont know if this answers your question but you don't really need the container entry at all. if you create a policy manually you can call the policy entry or container anything you want or just skip the container. It wont be managable with the console then (or pl script its probably safe to assume) which may be undesirable for you, but the policy itself will work. the only requirement is to set pwdpolicysubentry=... to point to your custom policy for your your users who wont use the default in cn=config, either directly on each user or more likely for the whole subtree using CoS pointers the same way the fedora-idm-console does it when you click on a subtree and choose to create a policy there.
I guess you could try to create a policy with the pl script or console, then export the policy entries to LDIF and modify to use escaping instead of double quotes then readd with ldapmodify after deleting the original entries, and see if the console/script can still "see" the policy. i would actually expect this to work if "cn=foo,dc=test,dc=com",dc=test,dc=com should be considered equal with dn: cn\=foo\,dc\=test\,dc\=com,dc=test,dc=com
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
