It would be great if we could add in extra LDAP fields so we could pull more information from Active Directory. Fields such as the users:
Currently only the users First and last name, their email address and AD username can be uploaded via LDAP sync.
Thank you for the great work you do.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Vote for this!
Vote for this! :D
+1 I would also like to see the ability to sync up more ldap/AD fields.
+1 this, too please
+1
+1
+1
Would love this as well!
+1
an addination;
+1
+1
+1
physicalDeliveryOfficeName
telephoneNumber
department
+1
employeeid/employeenumber
department
Hello @snipe
Is it planned in near future to integrate some more Active Directory fields?
Department, company, manager all get a little more complicated, since we would need to create those values if they didn't already exist. (For example, if your LDAP is listed as someone who doesn't exist in Snipe-IT, we have to check if that manager exists, and if not, create them.) That's fine for smaller OUs, but that LDAP sync is already doing a lot of heavy lifting, and the more work we try to do there, the longer it's going to take to process that info, leading to memory and/or timeout issues. It's the primary reason this hasn't been implemented yet.
@snipe What about giving the User the choice? For example - providing all those wanted fields. If the field Manager was let empty, you don't have to check for it if it exists or not. You could go on straight ahead. The Companies with large LDAP OUs can stick to the Fields they already use. They don't have to use the new provided fields if the sync is already that slow. But by providing those fields, samler OUs would benefit from it IMHO.
+1
Company
Country
Adress
telephoneNumber
department
+1 lets get this implemented :)
+1 Please Manager is must thing. So we can this snipe it to next level
+1 This feature is neccesary to implement LADP Sync since we use full-company-support.
Is not possible to set a Company field from LADP Sync, so the field is empty and need manual update in order to have a Company Id.
+1 to allow you to choose LDAP fields to import
Please update the above request I also have the same concern in my AD users.
Manager
TItle
Organization
Department
Phone number
TelephoneNumber
Employeeid/Employeenumber
@mahesh2471990 Your issue was solved ?
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
Need this extra LDAP Field.
From: stale[bot] notifications@github.com
Sent: Sunday, January 20, 2019 6:17:36 AM
To: snipe/snipe-it
Cc: neonGenesis7; Comment
Subject: Re: [snipe/snipe-it] Adding extra LDAP fields (#2853)
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/snipe/snipe-it/issues/2853#issuecomment-455838804, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlgejURUiGcNsRk5z8st7ZRPtLJd1_Gnks5vE_vwgaJpZM4Kkhd6.
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
Yes, it’s still relevant. Good bot.
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
+1. I want to import everything... EVERYTHING!
@kalidreamer given that we don't don't have custom fields for users yet, I'm not even sure what "everything" means.
Additionally, as I have explained in other threads, each one of the additional built-in fields adds processing time. Want to import a manager? First we have to check if that manager exists, and create them if it doesn't. Same for Department, Location, etc. This means potentially doubling or tripling the amount of work that LDAP import needs to do, which can result in timeouts, exceeding available processing memory, etc.
@mahesh2471990 Your issue was solved ?
no not yet
@kalidreamer given that we don't don't have custom fields for users yet, I'm not even sure what "everything" means.
Additionally, as I have explained in other threads, each one of the additional built-in fields adds processing time. Want to import a manager? First we have to check if that manager exists, and create them if it doesn't. Same for Department, Location, etc. This means potentially doubling or tripling the amount of work that LDAP import needs to do, which can result in timeouts, exceeding available processing memory, etc.
We want the Manager name should be synced by AD via LDAP.
and also during checkout and check-in if notification goes to the manager also it would be great
I would also love to be able to import many more fields. It would be great if I could select the fields I want to import.
Perhaps the system could provide the user with the option to skip any users with null properties in selected fields (this already seems to happen with the fields that are there), and/or put in a warning about potential hangs and timeouts if there are too many null values.
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.
Need this feature very much,thanks.
Most helpful comment
+1 lets get this implemented :)