[ADD] users_ldap_push #287
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hbrunn
force-pushed
the
8.0-users_ldap_push
branch
from
e2f1f42
to
cb7d73d
Compare
|
👍 (without test) |
hbrunn
force-pushed
the
8.0-users_ldap_push
branch
from
cb7d73d
to
4d9a733
Compare
hbrunn
force-pushed
the
8.0-users_ldap_push
branch
from
b1689a2
to
efffef0
Compare
| 'attribute': 'userid', | ||
| 'use_for_dn': True, | ||
| }), | ||
| ]) |
There was a problem hiding this comment.
is there a reason why you're not defining a dedicated default method and passing it as the default kwarg to the field?
|
@gurneyalex thanks for the review, most points fixed, the remaining points left to discussion |
|
👍 |
| attribute = fields.Char('LDAP attribute', required=True) | ||
| use_for_dn = fields.Boolean('DN') | ||
| ldap_id = fields.Many2one( | ||
| 'res.company.ldap', string='LDAP comfiguration', required=True) |
hbrunn
force-pushed
the
8.0-users_ldap_push
branch
from
00af230
to
6703b8a
Compare
|
@StefanRijnhart thanks, all points taken |
|
Thanks for the update 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Push users to LDAP
This module was written in order to use Odoo as a frontend for creating LDAP
entries by creating user records. Updates to the user record will be propagated
to the linked LDAP entry afterwards.
When users change their passwords, they will be updated in the LDAP directory
too.
Configuration
On the LDAP parameters of your company, check Create ldap entry in order to
activate this functionality. Be sure to configure a bind DN that has
appropriate permissions to create and modify entries.
Fill in the object classes newly created entries should contain, separated by
colons. Those classes will determine which mappings from Odoo fields to LDAP
attributes you need. This is highly dependent on your LDAP setup.
For a standard slapd setup, you might want to use object classes
inetOrgPerson,shadowAccountand the following mapping:========== ============== ==
Odoo field LDAP attribute DN
========== ============== ==
Login userid X
Name cn
Name sn
========== ============== ==
Matching is done by the new field ldap_entry_dn, so after installing this
module, you'll probably want to set this field. The module will write it when
a user logs in via Odoo.
Usage
When you create or update users, their corresponding LDAP entries will be
updated too.