Hello One Identity experts,
I hope someone can give me a hint for a challenge I'm facing:
I'm implementing backend validations for modifications on persons in the table scripts and column templates. Essentially this works quite well by throwing an exception with the end user relevance level.
But now comes the tricky part: I need to ensure, that the validation is only applied for changes originating from the new web portal (or the API server).
The API server uses a direct connection to the DB, so any information from QBMSessionStore isn't likely to help me. Also the Web Designer Web Portal will be running in parallel for a while and must be unaffected from the changes.
I was trying to rule out every other possible caller of the script/template but this gets quite exhaustive and I'm not even sure if I will be able to distinguish between the Web Designer Web Portal and the Angular Web Portal.
Do you have an idea for handling this scenario?
Env: One Identity Manager Version 9.2
I'm glad for every input, whether it's a conventional or a creative approach.
Kind Regards,
Florian
