ocis_ldap deployment example no longer works and requires documentation

[jvillafanez]

Describe the bug

I'd expect the example to show how to connect and use an external LDAP server. However, there seem to be undocumented requirements.
It's unclear whether we can use the entryUUID or objectGUID as IDP_LDAP_UUID_ATTRIBUTE. I remember we need to convert the data in order to search by that attribute in OC10, and I don't know if that's supported here. This would mean that we need to setup a different uuid attribute before connecting the LDAP server in oCIS.

In addition, the example uses the "bitnami/openldap" image, which isn't available any longer, so the provided docker example can't be build at the moment.

Steps to reproduce

1. Run docker compose up in the ocis_ldap example

Expected behavior

oCIS is up and running

Actual behavior

bitnami image isn't found and docker compose fails.

Setup

Please describe how you started the server and provide a list of relevant environment variables or configuration files.

OCIS_XXX=somevalue
OCIS_YYY=somevalue
PROXY_XXX=somevalue

Additional context

Add any other context about the problem here.

[jvillafanez]

Use an external LDAP

Following env vars needs to be adjusted

OCIS_LDAP_INSECURE: "true"

OCIS_LDAP_URI: ldap://server:14141
OCIS_LDAP_BIND_DN: "cn=admin,dc=owncloudqa,dc=com"
OCIS_LDAP_BIND_PASSWORD: password

OCIS_LDAP_GROUP_BASE_DN: "ou=groups,dc=owncloudqa,dc=com"
OCIS_LDAP_GROUP_FILTER: "(objectclass=groupOfNames)"
OCIS_LDAP_GROUP_OBJECTCLASS: "groupOfNames"

OCIS_LDAP_USER_BASE_DN: "ou=people,dc=owncloudqa,dc=com"
OCIS_LDAP_USER_FILTER: "(objectclass=inetOrgPerson)"
OCIS_LDAP_USER_OBJECTCLASS: "inetOrgPerson"

OCIS_LDAP_USER_ENABLED_ATTRIBUTE: "employeeType"
IDP_LDAP_LOGIN_ATTRIBUTE: "uid"

OCIS_LDAP_GROUP_SCHEMA_ID: "entryUUID"
OCIS_LDAP_USER_SCHEMA_ID: "entryUUID"
OCIS_ADMIN_USER_ID: "a73c6ea6-6e7c-103f-8110-dd19ecb0bb36"

NOTES:

• OCIS_LDAP_INSECURE should be set to false if possible. If you don't want to deal with SSL certificates, set it to true.
• The OCIS_LDAP_USER_ENABLED_ATTRIBUTE must exists and not be false. Empty / not filled values should consider the user as "enabled". The default value uses the ownCloud's schema that is unlikely to be present, so you might want to use a different attribute such as the "employeeType"
• OCIS_LDAP_USER_SCHEMA_ID and OCIS_LDAP_GROUP_SCHEMA_ID, same as above. "entryUUID" might be used instead.
  • "entryUUID" isn't an octet string and might not require the OCIS_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING (and group) flag. Double-check if that flag is needed (if you use AD's "objectGUID" attribute)
• The OCIS_ADMIN_USER_ID is based on the configured OCIS_LDAP_USER_SCHEMA_ID. In the case above, that would be the "entryUUID" of the LDAP user that will act as admin in oCIS.

Regarding the LDAP requirements, users might need the following attributes to be filled based on default configuration values in oCIS: "cn", "displayName", "mail", "uid"