Disclaimer: Some information in this article may be outdated, please verify details by referring to latest resources or reach out to our technical teams.
Introduction
In an effort to better enable both partners and customers, we have outlined a process that allows technically savvy customers the ability to make modifications to their JDBC provisioning rule without directly engaging IdentityNow's Expert Services team. We do not recommend this approach if you do not have the correct technical resources on hand with at least an intermediate level knowledge of Java.
Prerequisites
Elements of the project
Building a project structure
Within Eclipse, or any other IDE, your file structure should be as follows:
Make sure that you have imported the 'identityiq.jar' and you can see it in your Maven dependencies.
Elements of the Primary Java class
This is the foundation that handles our project. Every request initially comes here and then calls other methods.
Elements of the Auxiliary Java class
Clean Compile Package
The next step is to compile your Maven package. Upload the jar that is created to the source config.
Final Notes:
JDBC Rules can be very complicated depending on the source you are trying to connect to. We STRONGLY recommend that if you have any questions, bring them up to the Expert Services team for assistance.
Hello @leenaraj The issue is not fixed, I had raised this ticket to support team however no response from their side. A little disappointed.
Case - CS0211476 - Customer Support (sailpoint.com)
BTW: for the option1, it worked from my side now. however it is hard to develop/test/degug, so i would like to try this second solution.
https://community.sailpoint.com/t5/IdentityNow-Wiki/IdentityNow-Rule-Guide-JDBC-Provision-Rule/ta-p/...
Hi @Michael_Tai Until yesterday I was facing the issue where it was always picking the original jar, not the newly uploaded one. However, I just retried today and it is working totally fine, I can see it's picking the new jar.
Can you also retry it once and confirm if it's working for you now?
@leenaraj Thanks for sharing this.
From my side, even we tried to change the jar name/update some basic source information, however it does not work...
can we connect some times today or tomorrow? Not sure how we can connect in this community..
BTW: What kinds of changes you did recently ?
There are some recommendations from the SailPoint trainers, maybe we can raise support tickets to let sailpoint devops to remove the jars from backend, then we can re-try and i had done this just now, Let us see then @leenaraj
We are facing similar issue since last week, is there any solution suggested by Sailpoint? @Michael_Tai @leenaraj
@Anshu_Kunal There is no solution at the moment, we were trying to remove jar with SailPoint devops help from backend to see whether this issue had been fixed.
Hi @Michael_Tai @Anshu_Kunal , I had opened the support ticket for the same and it's fixed now. Please retry again by removing the old jar, save it and add the new jar. Also, you can run this command 'sudo docker exec ccg ls -l /opt/sailpoint/ccg/lib/custom' to check if the new jar is added.
Thanks for sharing @leenaraj We tried and find that orginial jar and it means that the updated jar does not uploaded in the pathe as your mentioned. Currently we do not have any permision on deleting since it is in the root folder. Which options you did and may i know what kinds of support case you raised and what kind of actions that SailPoint supported team did.
sudo docker exec ccg ls -l /opt/sailpoint/ccg/lib/custom