-
Notifications
You must be signed in to change notification settings - Fork 1
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
Wrong way to generate user name if AD id is empty #12
Comments
@stanbellcom, @skifter FYI |
@andriyun About your fix to add Also some comment about the proposed solution os2intra_user_import/includes/users.inc Line 63 in edc330e
will use `$user["employee_id"] to search user duplicats? And this line os2intra_user_import/includes/users.inc Line 368 in edc330e
$fields['name'] = $user['name']; ? and in case of ad_id activation method $user['name']= $user['ad_id'];
|
Added
Added additional check
See PR #13 |
During the user import process it's possible that
AD id
is emptyWe can have it in
employee_id
as activation method mode.With enabled
os2intra_generate_username
checkbox (see settings form) the code generate new ad_id in lineos2intra_user_import/includes/csv_mapping.inc
Line 72 in 066cfe0
and pass it to user name afterwards
os2intra_user_import/includes/users.inc
Line 368 in 066cfe0
Users generated in this way also got wrong
authorization
credentialsos2intra_user_import/includes/users.inc
Line 427 in 066cfe0
Proposed solution
For
employee_id
as activation method mode:Replace generation of new AD id to drupal user name
For
ad_id
as activation method mode:Skip user from import scope with proper log message
The text was updated successfully, but these errors were encountered: