Fully up to date on patches.
I'm trying to load users into the 389 server.
Here's how I made it (trimming the fs.inf file for
the sake of bandwidth):
Code: Select all
[root@fs ~]# dscreate create-template LDAP/fs.inf
[root@fs ~]# grep -v ^# LDAP/fs.inf | grep -v ^";" | uniq
[general]
config_version = 2
full_machine_name = fs.jgscrater.com
selinux = True
start = True
strict_host_checking = False
[slapd]
instance_name = fs
root_dn = cn=DirecMan
root_password = __deleted__
[backend-userroot]
Code: Select all
[root@fs ~]# dscreate from-file LDAP/fs.inf
[root@fs ~]# dsctl --list
slapd-fs
Code: Select all
[fs]
# Note that '/' is replaced to '%%2f'.
uri = ldapi://%%2fvar%%2frun%%2fslapd-fs.socket
###uri = ldap://fs.jgscrater.com:389
basedn = dc=jgscrater,dc=com
binddn = cn=DirecMan
Code: Select all
[root@fs ~]# dsidm -b dc=jgscrater,dc=com -D cn=DirecMan ldap://fs.jgscrater.com
:389 user cre
ate \
--uid jgs \
--cn jgs \
--displayName jgs \
--uidNumber 1000 \
--gidNumber 1000 \
--homeDirectory /home/jgs
Enter password for cn=DirecMan on ldap://fs.jgscrater.com:389:
Error: No such object
have to match the Directory Manager's password (it doesn't)?
Doesn't seem like that should be a requirement. Anyway, the password
that I give at the prompt doesn't complain about a bad password.
And if I deliberately give it the wrong password it does complain
about credentials.