Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In production env, we use an applet provided by a 3rd party vendor for 2FA login. We dont have any source code, have just the jar file. The applet basically encrypts the login info. Now it works well for most of the users, but few have problem with it using Java 7. It shows the message we put in the applet tag, which usually is being shown if browser doesn’t support Java. How to fix the issue on our own (without 2FA team support) as we only hold the jar file?
With great difficulty.
Unless you can identify the cause of the problem by a stroke of inspiration, you would need to decompile and reverse engineer the applet to try to figure out what is going wrong. There is a fair chance that the applet has been obfuscated to make reverse engineering harder, AND that the license you signed with the vendor forbids reverse engineering anyway.
Talk to the 2FA vendor support.