We currently have a request to integrate with Adobe Cloud and as mention in the vendor API Documentation, to effectively use the API, we need to sign our JWT every time we need to get an Access Token.
Our choice here is to use a WebServiceBeforeOperation to sign the JWT and change the Body of the Token Request. We use as an exemple this Rule from IIQ, but the VA does not load the jjwt.jar so we were unable to load the JWT using the class io.jsonwebtoken.Jwts.builder().
We manage to solve this problem by importing the jjwt.jar library into our /home/sailpoint/ccg/custom folder, once we manage to do that we could use the class and sign our JWT.
My question here is, there is a problem in putting .jar files on this folder? Does the VA will, in some future update, remove for some reason this .jar from the folder? If there is a problem in putting custom .jar files in this folder, what is the best approach to sign this JWT? Anyone here have made this integration with Adobe Cloud?
Would be great to here from the community the options that we have.
Upon each CCG service restart, the VA will remove any unknown jar files from the /home/sailpoint/ccg/custom folder. Only JAR files that are uploaded as part of a source configuration, like the JDBC source, will be allowed to remain. There is nowhere on the VA where you can manually upload a custom JAR. The only workaround for this is to create a new JDBC source that only exists to upload your custom JAR.
If you don’t mind, can you please submit an idea for this and post the idea link back in this topic? It would be great to see an option to upload custom JARs without having to use the JDBC source workaround.
That’s strange, I’ve made some tests and even after reboot the entire VA machine, the jar file does not get removed from the folder /home/sailpoint/ccg/custom. Any ideias on why this happens?
It looks like there are two directories where .jar files are stored. /opt/sailpoint/ccg/custom is where jar files uploaded from connectors are saved. If you add any custom jars to that directory, they will be removed upon next restart. However, /home/sailpoint/ccg/custom looks like it is provided for the purpose of uploading custom jars that stay after each reboot. The documentation isn’t clear on this, but it looks like you are safe to add your custom jars to /home/sailpoint/ccg/custom.
Good to know Colin, just to let this documented here, also made a test creating a JDBC Source, I did not configure any connection settings on the source, just upload de jar file, but it seems this didn’t do the trick, my Rule did not recognize the custom class.
Any way, we will follow with the /home/sailpoint/custom option.