===
GT: Did you have 61DUAConfigFile.ldif and 62nisDomain.ldif added to
config/schema (and slapd restarted)? They provides all the required
attributes for DUAConfigProfile and nisDomain objects including SSD
(serviceSearchDescriptor). We try not to touch 99user.ldif and the
original
I've copied some custom schema files to the config/schema directory. In
the Java console, some of the attributes and objectclasses defined in
the custom schema files show up under Standard, while others show up
in User Defined.
Does anyone know how FDS determines that an attribute or
George Holbert wrote:
I've copied some custom schema files to the config/schema directory.
In the Java console, some of the attributes and objectclasses defined
in the custom schema files show up under Standard, while others show
up in User Defined.
Does anyone know how FDS determines that
I would like to ask the people who are using the Fedora Directory Server
as a backend LDAP server to a Samba PDC to see what happens when a user
changes a password from the ctrl+alt+del dialog in Windows. (with 'ldap
passwd sync = Yes' in smb.conf)
This did not work for me the last time I
Yes it would be a superset containing schema definitions of
DUAConfigProfile and nisDomain attributes and objectclasses, ONLY if you
have run idsconfig. When I first tried configuring Solaris8 LDAP
Client against FDS I copied over the 99user.ldif from SUN iDS install,
and it actually worked.
BUT
