keep a bad subject log

Carey Black 2 hours ago
I finally tracked this down! (Ugh)
I found a loader job that was pulling in a group from a System of Record that showed a “unresolvable subject” for the loader job. ( It happened to be an SQL loader job too. )
So I double checked the Subject ID’s from that table with my subject source (GSH script to loop over 17k subject ID’s and throw on any errors… one popped out as “Search is not unique” !?!?!
---> The LDAP Subject source had a duplicate for that Subject ID value!
Ugh. I reported it to our IDM team, they fixed the data.
And this AM.. my report now shows:
“unresolvable subjects: 0”
Yea! Order is restored to the Universe!
Just wanted to close the thread incase it helps anyone else find errors in their Universe like that. :slightly_smiling_face:
P.S. It would be much more ideal if such an error condition could be “forcibly logged” ( AKA: printed to a ’bad_subjects.log” file at all times) to make such things “much easier to find” too. :slightly_smiling_face: