We tried to implement DRS also. But even DRS is also Not working. With Java 8
update 40 we are able to access the application without any issues. The issue
starts with Java 8 update 45.

We have an application which is not working with the latest versions of Java
8. It is to be noted that this application requires user login. When the user
logs in normally he is able to access the application. However, The same
application is not opening when the user logs in with his smart card.

We have done some tests here and found out that the issue started with Java 8
update 45. We have also created a new rule in Deployment Rule set, which will
enable the application to open with Java 6. After the new rule is deployed,
The application opens with Java 6 when the user logs into the application
with a normal login. However, if the user logs in with the help of a smart
card, the application doesn't open with Java 6. It still opens with Java 8.

We have tested the application with Java 8 update 40 and it works fine
without any issues. We would like to know the changes introduced in the Java
8 update 45 with relation to smart card.

Using 8U40 application works fine.
Using 8U45 the issue started happening.
What are differences are introduced in 8U45 around smart card.
All the desktops in UBS, many users use different applications.
They want to make sure that there are No issues after the roll out.

Observation:
java 8U40, client cert is shared twice
java 8U45 client cert is shard only once

We have dome some more tests and here is the analysis from us.

In working trace from 1.6 update 95 and smart card:
- client certificate was shared twice.
- Java.exe process was seen making calls to bw.inventories.it.ubs.com:443

In Non-working trace with java 1.8 update 45 (with Package and Base msi):
- client certificate was send only once
- Jp2launcher.exe process was seen making calls to bw.inventories.it.ubs.com:443

We have found that site is launching fine with java 1.8 update 5 ( Base msi)
and smart card

- Client certificate was shared twice.
- Java.exe process was seen making calls to bw.inventories.it.ubs.com:443

The application was working with Java 7 update 55 and was not working with
update 7U79. The username is not visible in jar file download request