-
Notifications
You must be signed in to change notification settings - Fork 0
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
LDAP Check #37
Comments
Every now and then we need to check the status of accounts in Activity Insight, we download the list of active users that are staff and faculty. We have the ability to cross check most faculty from a report pulled from Workday, but we are finding that we have to cross check faculty and staff at http://www.work.psu.edu/ldap/ because the faculty may not be appearing in our list. Sometimes the number of faculty/staff we need to double check can be 200 or more and as you can imagine that would take us a lot of time. What I would like to do is to upload a csv file that contains First Name, Last Name, and PSU Access ID to the FAMS Tool, and it check "ldap" and then update the file we uploaded with the following fields: I will then use these results to disable or enable faculty accounts. |
Just from first pass:
|
After talking to Nicole: Have the integration take a CSV (which will follow what the example will be), pull relevant info from central LDAP (as defined in this issue), THEN also have the option of disabling (not deleting) faculty if eduPersonPrimaryAffiliation is "member". If this functionality is requested (maybe some sort of button or switch in the front end, sent as a boolean flag), the CSV will also indicate which faculty account has been disabled (a new column, something like |
Here is the file we would submit via the tool. We want to make sure if LDAP returns Member they then get disabled in Activity Insight, but if they can't be found in LDAP the response back can be user not found. |
Include whether or not an user is already disabled. Get this info even when not disabling. |
No description provided.
The text was updated successfully, but these errors were encountered: