[doc/fix] you need a blank line after ::

This commit is contained in:
Laurent Peuch 2019-08-04 19:06:00 +02:00
parent f1ac5b8fe6
commit df7d47831b

View file

@ -226,6 +226,7 @@ According to :file:`ldapvi` this is the user schema (on YunoHost >3.4):
The groups will look like this: The groups will look like this:
:: ::
dn: cn=the_unix_username,ou=groups,dc=yunohost,dc=org dn: cn=the_unix_username,ou=groups,dc=yunohost,dc=org
objectClass: top objectClass: top
objectClass: groupOfNamesYnh objectClass: groupOfNamesYnh
@ -238,6 +239,7 @@ The groups will look like this:
By default you will find in all case a group named `all_users` which will contains all Yunohost users. By default you will find in all case a group named `all_users` which will contains all Yunohost users.
:: ::
# path dn: cn=all_users,ou=groups,dc=yunohost,dc=org # path dn: cn=all_users,ou=groups,dc=yunohost,dc=org
objectClass: posixGroup objectClass: posixGroup
objectClass: groupOfNamesYnh objectClass: groupOfNamesYnh
@ -257,6 +259,7 @@ The group schema is located at this path: :file:`ou=groups,dc=yunohost,dc=org`
The queries we uses are the 2 following python calls: The queries we uses are the 2 following python calls:
:: ::
# all groups # all groups
auth.search('ou=groups,dc=yunohost,dc=org', '(objectclass=groupOfNamesYnh)') auth.search('ou=groups,dc=yunohost,dc=org', '(objectclass=groupOfNamesYnh)')
@ -272,6 +275,7 @@ According to :file:`ldapvi` this is the user schema (on YunoHost >3.4):
The permission will look like this: The permission will look like this:
:: ::
dn: cn=main.mail,ou=permission,dc=yunohost,dc=org dn: cn=main.mail,ou=permission,dc=yunohost,dc=org
objectClass: posixGroup objectClass: posixGroup
objectClass: permissionYnh objectClass: permissionYnh
@ -292,6 +296,7 @@ The permission schema is located at this path: :file:`ou=permission,dc=yunohost,
The queries we uses are the 2 following python calls: The queries we uses are the 2 following python calls:
:: ::
# For all permission # For all permission
auth.search('ou=permission,dc=yunohost,dc=org', '(objectclass=permissionYnh)') auth.search('ou=permission,dc=yunohost,dc=org', '(objectclass=permissionYnh)')
@ -437,6 +442,7 @@ Get conflict
Like the last function `validate_uniqueness` but give instead of rising an error this function return which attribute with witch value generate a conflict. Like the last function `validate_uniqueness` but give instead of rising an error this function return which attribute with witch value generate a conflict.
:: ::
# Validate uniqueness of groupname in LDAP # Validate uniqueness of groupname in LDAP
conflict = auth.get_conflict({ conflict = auth.get_conflict({
'cn': groupname 'cn': groupname
@ -509,6 +515,7 @@ The option `force` of the function `permission_sync_to_user` is used when you ad
To be able to have an attribute in both is of theses 3 link we use the `memberOf` overlay in LDAP. This following line define the configuration to have these 3 link dynamically updated : To be able to have an attribute in both is of theses 3 link we use the `memberOf` overlay in LDAP. This following line define the configuration to have these 3 link dynamically updated :
:: ::
# Link user <-> group # Link user <-> group
#dn: olcOverlay={0}memberof,olcDatabase={1}mdb,cn=config #dn: olcOverlay={0}memberof,olcDatabase={1}mdb,cn=config
overlay memberof overlay memberof
@ -552,6 +559,7 @@ LDAP integration in Yunohost applications
To have a complete integration of LDAP in your application you need to configure LDAP as follow : To have a complete integration of LDAP in your application you need to configure LDAP as follow :
:: ::
Host: ldap://localhost Host: ldap://localhost
Port: 389 Port: 389
Base DN: dc=yunohost,dc=org Base DN: dc=yunohost,dc=org