You will have to maintain this contribution for future Nuxeo upgrades. If you need to add other custom setting where the template doesn't define any variable for that config then the second option would be better. If changes are required then the template will be automatically updated at the future upgrades. The advantage of that solution is you don't have to deal with future upgrades config changes as you simply define variables in nf. The first approach allows you to simply reuse the default LDAP configuration template here by providing values for each variable defined in this template. Providing an XML contribution for your LDAP configuration.Set all out-of-the-box LDAP variables in nf.There are 2 ways to define your LDAP configuration: This is done using the administratorsGroup element. You can also choose a group from your company's directory instead of using the default "administrators" group, to determine the users who will benefit from all the rights in the platform. This is done using the defaultAdministratorId element. On the same contribution to the UserManager extension point you can define which principal from the remote identity provider will be the administrator of the application, instead of Administrator. īy default, the platform's administrator is the principal "Administrator". Groups are defined on the groups element (also referencing already contributed directory). The value somedirectory is the name of a contributed directory (see LDAP and SQL users contributions, as well as multidirectory). Here is a review of the specific useful parts. You can find a full example of contribution to the userManager extension point on the explorer. Since groups are used in Nuxeo to associate permissions with content, fetching groups from LDAP is usually not very efficient: LDAP groups are usually not designed for that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |