mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2024-12-23 07:33:27 -06:00
c00281a9f9
We want to process some updates in a particular order (schema, structural). Using an init-inspired ordering mechanism.
34 lines
976 B
Plaintext
34 lines
976 B
Plaintext
#
|
|
# Add profile for RFC 4876 agents (Solaris and HP/ux)
|
|
#
|
|
|
|
# Update the top-level entry
|
|
dn: $SUFFIX
|
|
add:objectClass: domain
|
|
add:objectClass: domainRelatedObject
|
|
add:objectClass: nisDomainObject
|
|
add:associatedDomain: $DOMAIN
|
|
add:nisDomain: $DOMAIN
|
|
|
|
# Add a place to store the nss_ldap default profile
|
|
dn: ou=profile,$SUFFIX
|
|
add: objectClass: top
|
|
add: objectClass: organizationalUnit
|
|
add: ou: profiles
|
|
|
|
# The DUA profile. On Solaris one can run:
|
|
# ldap_client init ipa.example.com
|
|
dn: cn=default,ou=profile,$SUFFIX
|
|
default:ObjectClass: top
|
|
default:ObjectClass: DUAConfigProfile
|
|
default:defaultServerList: $FQDN
|
|
default:defaultSearchBase: $SUFFIX
|
|
default:authenticationMethod: none
|
|
default:searchTimeLimit: 15
|
|
default:cn: default
|
|
default:serviceSearchDescriptor: passwd:cn=users,cn=accounts,$SUFFIX
|
|
default:serviceSearchDescriptor: group:cn=groups,cn=compat,$SUFFIX
|
|
default:bindTimeLimit: 5
|
|
default:objectClassMap: shadow:shadowAccount=posixAccount
|
|
default:followReferrals:TRUE
|