Automating Code Signing with multiple E-Business Suite instances - Part 3

Automating Code Signing with multiple E-Business Suite instances - Part 3

Johannes Michler PROMATIS Horus Oracle

Executive Vice President – Head of Platforms & Development

As you are probably aware by now, since June 1st 2023 all well-known / public Certificate Authorities (CA) no longer provide Code Signing Certificates using pure software based private keys (see

Since I prefer using such a trusted / public CA to sign Java Applets (that are still crucial for Oracle E-Business Suite or Oracle Forms) I've recently had a look into how we can now sign those Java JAR files. Part 1 of this blog series introduced the topic and an available "Cloud Based" Code Signing Certificate provider: Signing EBS/Forms - Part 1

In a second part I covered how the code signing can be done on an E-Business Suite Application Server running on Oracle Linux 7 on Oracle Cloud Infrastructure (OCI).

This third post will look how we can further automate this by installing the Certum tools onto the E-Business Suite Cloud Manager VM. First, we'll cover the latest changes from Certum, then we'll look into some scripts that can be used on multiple E-Business Suite Application servers to send the .jar files for signing to that central signing instance.

Certum Tool updates (April 2024)

Back in the previous post, I've complained about the incomplete translation of the Certum tools still revealing a lot of polish error messages. While it seems this is fixed at least partially, I realized that the 2.9.9 versions available over there leads to fatal crashes (segmentation fault). That is why for now I stuck with the 2.9.8 release.

Installing Certum SimplySignDesktop as a non-root user

When installing the SimplySignDesktop tool according to the official documentation it is necessary to do so globally/as the root user. Since I didn't like the tool to modify my cloud manager VM in that massive way, I've investigated what the installer actually does. With that I was able to get the tool running with a way less privileged user (that I call certum). Run the following as root:

yum install
yum install libxslt.x86_64 pulseaudio-libs-glib2.x86_64 libwebp.x86_64 xkeyboard-config
useradd certum
sudo su – certum
mkdir .ssh
vi .ssh/authorized_keys
# add the SSH public key(s) of your oracle@ebs-appserver
chmod 700 .ssh
chmod 600 .ssh/authorized_keys

Then connect a SSH Session with X-Forwarding as certum:

sh SimplySignDesktop-2.9.8- --target /home/certum/
cp /home/certum/SSD-2.9.8-dist/SimplySignDesktop.xml /home/certum/

Create a /home/certum/provider_simplysign.cfg file as follows:


Furthermore, create a script as follows:

export LD_LIBRARY_PATH=/home/certum/SSD-2.9.8-dist/
export QT_QPA_PLATFORM_PLUGIN_PATH=/home/certum/SSD-2.9.8-dist/plugins
export OPENSSL_CONF=/etc/ssl/
stalonetray &

Finally start the Script and sign in with a one-time-token.

Do a test as follows (in new SSH Session):

/home/certum/SS- -list -keystore NONE -storetype PKCS11 -providerclass -providerArg /home/certum/provider_simplysign.cfg -v

This will provide an alias, in our case: 4F4F410D1234A9110B16DA9C83BD6F59

Furthermore, create a /home/certum/mychain.pem file as described in the previous episode.

Passing the jars

On the E-Business Apps-Server first create a ~/ script as follows:

folderstamp=$(date +%Y-%m-%d-%H:%M)
mkdir -p /home/oracle/sign_bkp/${folderstamp}
# Remove Signature from jar files created through ADADMIN in EBS
echo " ** Removing EBS signature from: ${jar} "
cp -i ${jar} /home/oracle/sign_bkp/${folderstamp}/
zip -d ${jar} 'META-INF/*.SF' 'META-INF/*.RSA'
scp ${jar} certum@

ssh certum@ "/home/certum/SS- -keystore NONE -tsa \"\" -certchain /home/certum/mychain.pem -storetype PKCS11 -providerClass -providerArg /home/certum/provider_simplysign.cfg -storepass 12345 /tmp/signing-dummy.jar 4F4F410D1234A9110B16DA9C83BD6F59"

scp certum@ ${jar}

The script first creates a backup of the jar, then un-signs the .jar files and copies it to the cloud-manager VM (in my case with IP There the jar is signed and finally the signed .jar is copied back to the E-Business Suite Apps Tier.

This allows signing a single .jar file; the script may be helpful when applying a patch with "options=nojarsigning". Then in there should be a file such as /u01/install/APPS/fs_ne/EBSapps/log/adop/176/20240327_132920/apply/mastebsapp01/36177213/log/jarlist.txt containing all the .jar files that require re-signing.

For the initial signing the procedure in the previous episode can be combined with the copying of the .jar to the Cloud Manager VM.

Verifying and patching

As an alternative to signing "just" the files in $NE_BASE/EBSapps/log/adadmin/log/jarlist.txt I found it useful to just sign all .jar files under $JAVA_TOP. For this the following script proved helpful:

folderstamp=$(date +%Y-%m-%d-%H:%M)
mkdir -p /home/oracle/sign_bkp/${folderstamp}
# Select the jar files from jarlist.txt
for jar in $(find $JAVA_TOP/oracle/apps -name \*.jar)
# Remove Signature from jar files created through ADADMIN in EBS
echo " ** Removing EBS signature from: ${jar} "
cp -i ${jar} /home/oracle/sign_bkp/${folderstamp}/
zip -d ${jar} 'META-INF/*.SF' 'META-INF/*.RSA'
scp ${jar} certum@
ssh certum@ "/home/certum/SS- -keystore NONE -tsa \"\" -certchain /home/certum/mychain.pem -storetype PKCS11 -providerClass -providerArg /home/certum/provider_simplysign.cfg -storepass 12345 /tmp/signing-dummy.jar 4F4F410D1234A9110B16DA9C83BD6F59"
scp certum@ ${jar}

It is helpful to first to a check if the $jar is already signed as follows:

result=`jarsigner -verify -certs ${jar}| tr -d '[:space:]'`
if [[ "jarverified." != "$result" ]]
echo ${jar} needs re-sign; $result
# put the signing here


Using above scripts, it is amazingly easy to sign all .jar files both initially as well as after applying a patch. The version using a "find" on $JAVA_TOP may sign "a bit more than needed", but in my experience that does not do any harm.

I am still hoping that Oracle will provide a way to "Hook" a script such as into the signing process called during patching or through adadmin. This would probably be announced in "Signing EBS Jar Files With HSM (Hardware Security Module) - (Doc ID 2806640.1)".

PROMATIS continues on its expansion course

PROMATIS continues on its expansion course

Global partnership – PROMATIS joins forces to pursue its growth strategies

Ettlingen, 04/04/2024The business process innovator announces that it has joined the International Technology Group B.V. (ITG), a partnership of Oracle service providers whose complementary portfolios are optimally interconnected. Supported by investor IceLake Capital, PROMATIS is thus benefiting from a stronger market position and the implementation of growth strategies in terms of international expansion. This global partnership positions PROMATIS – specialist for intelligent business processes and Oracle digitization solutions – for accelerated growth with global scalability and simultaneous diversification of services. For customers, the new organizational structure offers enormous advantages in terms of future security, innovative strength and, above all, in the Managed Services & Support division.

Seizing new opportunities and preserving the tried and tested was PROMATIS' intention in joining ITG, a holding company of Dutch financial investor IceLake Capital. The previous shareholders of the PROMATIS Group transferred their shares in the company to this internationally active holding company based in Amsterdam, thereby underlining the steady growth of the group of companies. Dr. Frank Schoenthaler, CEO of PROMATIS Group, and the entire executive management will continue to perform their functions in the coming years. Schoenthaler will also be a member of the Executive Committee of the holding company. In this respect, the continuity of PROMATIS' operations, including the organizational structure and all employees, is secured for the coming years.

In addition to innovative digitization expert PROMATIS, two other strong Oracle partners are united under ITG: Quistor and Project Partners. By bringing together three of the most important Oracle solution providers in the international environment, investor IceLake Capital has succeeded in creating a perfect alignment for this market segment. The strategic alliance also identifies and taps into extraordinary synergy potential. This launch into a new era of performance means an extended geographical reach, comprehensive expert know-how in modern business applications and bundled Oracle clout. This Oracle Competence Center of the new dimension is predestined to meet increasing customer requirements and form a leading IT platform. By joining forces, new capacities will be freed up, such as an advanced and outstanding 24/7 managed services offering for functional and technical support around the clock.

“With its new size, PROMATIS is now armed with substantially enhanced capacities compared to previously, establishing a stronger stance that affects both its capability and financial power. Our customers benefit considerably from this, and it opens up completely new ways of establishing process innovations in the company,“ Dr. Frank Schoenthaler says, CEO of PROMATIS Group.

The global solution provider PROMATIS is based in Germany in the Karlsruhe TechnologyRegion with branches in Hamburg and Muenster (Westphalia), as well as country offices in Austria (Vienna), Switzerland (Zurich), Croatia (Zagreb) and the USA (Denver, CO). A lively network of partners in business and research guarantees implementation strength and a high level of innovation.
Our experience includes Oracle Cloud Applications (incl. Fusion), NetSuite ERP and Oracle E-Business Suite as well as the Oracle Technology Stack on Prem, Cloud and hybrid. With proven process models, project tools and country- and industry-specific Best Practice solutions, we ensure that our customer solutions are cost-effective and future-proof. You can find more information about PROMATIS at

About IceLake:
IceLake Capital is a private equity firm that invests in exceptional companies and focuses on helping mid-sized companies become international market leaders in their respective industries. These companies have a strong market position and benefit from support in the effective implementation of their global growth ambitions, such as buy & builds and international expansion. You can find more information at

About Quistor:
Founded in 2005, Quistor is known for its profound experience in JD Edwards, Oracle Infrastructure as a Service, Oracle Platform as a Service, Oracle Autonomous Data Warehouse and Oracle Analytics Cloud technology. The company’s mission is to deliver outstanding Consultancy & Managed Services. Quistor currently serves over 250+ clients globally and staffs around 250 people with offices in the Netherlands, Spain, Czech Republic, France, Mexico, United Kingdom and the Philippines.. Quistor has won several awards for its Oracle Autonomous Datawarehouse, Oracle ERP and Oracle Cloud expertise. For more information about Quistor, visit its website at

About Project Partners:
Project Partners is dedicated to project-centric organizations around the globe since1997. As a full-service project technology and management consulting agency they are helping organizations across many industries deliver excellence in their project technology lifecycles from start to finish, on time, and within budget. Project Partners specializes in Oracle ERP Applications (on prem and Cloud) and a variety of Project Management and Execution Solutions. 78+ global consultants incl. 20+ experienced partners support multi-geographical operations in 19+ countries and execute implementations for organizations that manage 10,000+ projects with thousands of users who utilize multiple languages and currencies. Project Partners experience spans project modules of Primavera, Kahua, E-Business Suite, Fusion ERP, JD Edwards. You can find more information at


Oracle Announces Fiscal 2024 Third Quarter Financial Results

A few days ago, Oracle Corporation announced its results for the third quarter of the 2024 financial year.

Oracle Corporation (NYSE: ORCL) today announced fiscal 2024 Q3 results. Total quarterly revenues were up 7% year-over-year in both USD and constant currency to $13.3 billion. Cloud services and license support revenues were up 12% in USD and up 11% in constant currency to $10.0 billion. Cloud license and on-premise license revenues were down 3% in both USD and constant currency to $1.3 billion.

Read the full press release here

Automating Code Signing with multiple E-Business Suite instances - Part 3

Accessing E-Business Suite Cloud Manager APIs - IDCS Token Management

Johannes Michler PROMATIS Horus Oracle

Executive Vice President – Head of Platforms & Development

Previously (, I described how you can use (unofficial) APIs to fully automate E-Business Suite environments hosted with Cloud Manager on Oracle Cloud Infrastructure (OCI). As you can see there, the actual call to trigger a clone or also the termination of an environment is rather simple. I've recently used that a lot when I worked on my clone scripts. In that process, I had to create ~10 clones, and doing so with a simple REST call saved me a lot of time.

In said post, we got hold of a "OAuth Bearer Token" that is needed to call those APIs in a very manual way "through the browser". In real life, this does not really come in handy. This blog post will describe how a bearer token (including a refresh token) can be received through the command line.


In preparation for using the scripts shown below, we have to enable the usage of "Device Codes" for the Cloud Manager application in IDCS:

Definition of Cloud Manager application in IDCS

Furthermore you should take note of the client_id, the client_secret and the IDCS url. All 3 have also been used during Cloud Manager setup.

A piece of Code

First of all, the following shell script does all the magic needed. You have to replace XXXXX, YYYYY and ZZZZZ with values from your environment:


PASS_ENC=`echo -n "$CLIENT_ID:$CLIENT_SECRET" | base64 -w 0`


if [ -f "mytoken" ]; then
REFRESH_TOKEN=`cat mytoken | jq '.refresh_token'| tr -d '"'`
echo refresh token: $REFRESH_TOKEN
BEARER_TOKEN=`curl -K -i -H 'Authorization: Basic '"$PASS_ENC"'' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST $IDCS_TOKEN_URL -d 'grant_type=refresh_token&refresh_token='"$REFRESH_TOKEN"`
cp mytoken mytoken.old
DEVICE_INFO=`curl -K -i -H 'Authorization: Basic '"$PASS_ENC"'' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST $IDCS_DEVICE_URL -d 'response_type=device_code&'"$CLIENT_ID"`
DEVICE_CODE=`echo $DEVICE_INFO | jq '.device_code'|tr -d '"'`
echo identified DEVICE_CODE $DEVICE_CODE press enter when done
BEARER_TOKEN=`curl -K -i -H 'Authorization: Basic '"$PASS_ENC"'' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST $IDCS_TOKEN_URL -d 'grant_type=urn:ietf:params:oauth:grant-type:device_code&device_code='"$DEVICE_CODE"`

echo $BEARER_TOKEN > mytoken
ACCESS_TOKEN=`echo $BEARER_TOKEN| jq '.access_token'| tr -d '"'`

# call the rest api to get shapes

curl -k -X GET $CLOUDMGR_URL/ebs/shapes/networkProfile/MY_AD2 -H 'Authorization: Bearer '"$ACCESS_TOKEN"''

First running the script

When you call this script for the first time, it gives an output as follows:


identified DEVICE_CODE 483150ce7704487da495593d1c97c2a4 press enter when done

Just open the verification URI provided in a browser, sign in to IDCS and pass the user_code CTHJNLAM.

Then, return to the shell script and press return. This will allow the script to get a Bearer Token including a Refresh token.

Subsequent runs

On every subsequent run, the "previous" refresh token (stored in the file mytoken) is exchanged for an access token and a new refresh token. That new refresh token is saved (each refresh token is a one-time-use token) and can then be used for the next run.

Using the access token we received through that way, we can conveniently access the Cloud Manager APIs.


With the above way, you can get a token that is valid for at least a week. For most operations this should be sufficient; if not, these timings can be extended in IDCS. See for more details on that (OAuth Refresh Token Expiry).

The combination of the procedure described in this and the previous blog post allow a simple and complete end-to-end automation of clones - e.g. on a nightly basis.