-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding featureId to ldap schema #90
Conversation
@RemiDesgrange can you refresh my memory - why was this contributed originally ? |
1.2.2 is not "featureId" anymore, relying on the current state of the geOrchestra LDIF schema, it should be "georchestraObjectIdentifier" and should match a UUID: https://oid-base.com/get/1.3.6.1.1.16.1, cf: And I am wondering: Shall we have a documentation for every attributes being used in the georchestra schema, or just pointing to the LDIF in the source tree should be considered sufficient as documentation ? |
updated current branch, see last commit. |
Update the documentation page, so that it reflects the current state of the custom georchestra LDAP schema described here as LDIF format: https://github.com/georchestra/georchestra/blob/master/ldap/docker-root/georchestraSchema.ldif
rebased on master (hence the push-force). |
GHA is failing, but this does not look like related to this PR, some errors are about the X/twitter account. |
No description provided.