Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

MODIFYUSERDATAJSON not working anymore since upgrade v23.9

Caesrob
Regular Contributor
Regular Contributor
Since upgrading to v23.9, our MODIFYUSERDATAJSON with an external JAR isn't working anymore.
This would fill in customproperty7, customproperty8, customproperty9, customproperty10 and customproperty11 for new and existing users using the information we got back from our customers HR source. This would be done through calculations in JAVA code in our external jar job.
 
I will attach 2 files: 1 file (oldlogs) contains logs from when this was working, the other (newLogs) contains logs from our import today.
Note that the logs which were working are older than when we upgraded, but we couldn't find any logs from just before that time frame. 
Open both files and search for "Proceed to Import for records - > [student1@student.uhasselt.be".
As you can see in the old logs, at the end of the line the custom JAR job fills in the customproperties
 
Caesrob_4-1697543061528.png
When we take a look at the new logs and search for the same query, we see that at the end of the line every value the custom JAR job should fill in is "NULL"
 
Caesrob_3-1697543036110.png
 
Another thing we noticed is this:
When we look at the old logs and search for "Logs info", we can see 3 lines being printed saying "Logs info:", "Logs warning:" and "Logs severe:". These outputs are printlns we wrote in our external JAR to check if the JAR was correctly being used (and it was).
 
Now check the new logs and search for "Logs info", you can't find it. These 3 lines which should be printed are not being printed in the logs anymore (Someone told us Saviynt deprecated this because of security reasons but we didn't find anything about this in documentation).
 
Again, we haven't changed ANYTHING since this was first working. 
We have tried restarting the services and checking the logs for errors but couldn't find any.
 
The last user which was successfully imported was on 19/09/2023. We received the upgrade to version 23.9 on 21/09/2023. We didn't run the job for a few days after that and on 24/09/2023 we saw it was broken.
1 REPLY 1

SB
Saviynt Employee
Saviynt Employee

Since this broke after a version upgrade, I would recommend creating a ticket with support team.


Regards,
Sahil