Duplicate PIDMS
Wed, 2008-07-16 10:36 — peluso14
We are in pre-production and one question that has not come up until now, is how does Luminis deal with a person delete out of banner, sometimes, not to often we get duplicate persons in banner, and we must merge two or three pidms into one, is there a mechanism to delete persons from luminis via a LDIPERSON event or is this a manual process?
Hack Your Knowledge
Recent blog posts
- Adding a Tab - disable this feature
- Cleaning entered username at login
- Cross platform migration
- Banner SSB Channels
- Alternative for inline frame channels?
- Luminis channel errors
- Facebook Channel - Non-Portlet
- AppServer Installation Errors
- Luminis 3.3 to 4 Migration properties questions/thoughts...
- Proxy Settings on Luminis
Developer Links
Poll
What version of Luminis are you on (Production)?
Luminis III.3.3.x
50%
Luminis 4.0.x
24%
Luminis 4.1.0.x
20%
Luminis 4.x
5%
Luminis 5+
0%
NONE : We ditched Luminis for static HTML! (it was more functional and doesn't crash)
1%
Total votes: 104
Syndicate
Deletion
It appears that the LDI mechanism does not send any delete messages from Banner. Not only should it happen under the circumstances you describe, but it also should happen when a user has all of their roles removed. Of course the problem is not knowing what to do if they have roles not defined by Banner data.
good question
Hi,
we have a lot of duplicate PIDM issues. We just migrated to Banner and we had a lot of problems with students/faculty/employees having multiples banner ID's. We consolidated all their banner ID's under one PIDM. That PIDM is the Banner primary ID and all the others are secondary ID. This was conveyed to our end-users through email (about teh consolidation of their multiples ID's into one primary ID and other alternate ID's).
In luminis the person's primary ID is reflected. In luminis, as far as i know there is no way of knowing a person's alternate ID (Please correct me if i am wrong). Because of the rules defined in GORRSQL, if the person has multiple ID's it probably would mean that the person has multiple roles. Luminis does get that information from banner(about multiple roles). Now the problem is when the user with multiple tries to do a SSo to applications available to all those roles (since most SSO's take their banner ID into consideration and luminis doesn't store their alternate ID's). I would love to find a solution to this problem.
Also my experience with Banner is very limited - so please excuse me for my ignorance. i was under the impression that accounts never get deleted from banner. They are just attached with an end date. So far i have never encountered with an account being deleted from banner and i dont see a reason why an account should be deleted from banner.
But it is an interesting question though - if an account is deleted from banner what kind of message will be relayed to luminis.
But so far, we never encountered duplicate PIDM situation or delete an account situation. Would you please let me know when can somebody expect a duplicatet PIDM scenario and deleting an account scenario?
Thank you,
Shiva
pidms
If a person is entered into banner with pidmA, an event goes across to Luminis creating PersonA with PidmA
If later, a duplicate record is accidently created for PersonA, with PidmB, an event will go across to Luminis with PersonA and PidmB, and it will error saying:
WebServlet.cp$cpincoming-adapter: ERROR processing PERSON entity with identifier 'login.name'
': SourcedID cannot be modified after initially set: curValue='PidmB', value='PidmA'
That is found in the datapipeline-main.log usually. All events for PersonA PidmB will be rejected by Luminis.
So you need to be careful that the Banner people let the Luminis Admin know when a duplicate is found, and the Luminis Admin needs to make sure that the PIDM in the luminis ldap matches the PIDM in the Banner record.
That, or the Banner people need to always use the old record if a dupe is found.