Closed christopherpickering closed 1 year ago
I had modified the code on our end for the ldap extract to do just this. This is what we have in our paged_search: generator = conn.extend.standard.paged_search( SUFFIX, search_filter="(objectCategory=user)", search_scope=SUBTREE, attributes=["*"], paged_size=1000, generator=True, )
Nice! thanks for the example! Are you running the other etls? It would be great to talk more sometime.
@paysni I would appreciate it if you could check out the dev branch.
I renamed most of the env vars, changed to ldap search strings, added profile photos, and clean up some junk.
The cn and ou regexs in the user section can probably be replaced with the utils function from the ldad3 libaray to be a bit cleaner, but maybe another day.
@christopherpickering it works for us. I like being able to choose the fields in the .env file. For example we store phone in telephoneNumber field before ipPhone.
I noticed you had LDAP_USER_SEARCH twice in your example .env file but that doesn't cause an issue. Might want to remove it though.
We are also using all the Tableau ETL, Solr-Search ETL, and bi-library ETL package. It would be great to talk more sometime. I can be reached at payton_snider@valleymed.org
I noticed you had LDAP_USER_SEARCH twice in your example .env file but that doesn't cause an issue. Might want to remove it though.
ops, thanks!
:tada: This issue has been resolved in version 2.0.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Feature Request
It would be nice to use a ldap search query to pull in users instead of having to specify multiple bases.