#Configuring Java Db Serial Number Of#

Security features in OS X/MacOS and Java itself will often disable (or lock down) previous versions of the Java plugin from working in your browser.It is very important to always keep your Java installation up to date. New java updates are pushed out regularly, and it is important to keep up to date.When new Java updates are made available, your old version my stop working properly. If Java cannot be detected, you must fix the problem before you can proceed further.We recommend that you always have the latest version of Java installed on your Mac. You can check to see if java is working properly in your browser with the following web sites:Screenshot from the official Java web site.One (or both) of the pages listed above MUST be able to detect Java before any DBsign enabled web site will work.

This gives DBsign all the permissions it needs to run properly. In the drop down box to the right of the web site address, choose 'Run in Unsafe mode'. You you click on the button, you will see something like this: Safari 9 (and earlier)Locate each web site that uses DBsign in the list (our demo.dbsign.com site, the Defense Travel System site, etc). Here, you will see a button that says 'Manage website settings.'. For this reason, DBsign will not run in Chrome on OS X/MacOS.In order to grant the necessary permissions to web sites running DBsign, we must edit Safari's security preferences.From the 'Safari' menu, choose 'Preferences'and then go to the 'Security' tab. Safari and Firefox both support the Java plugin however, Chrome is a 32-bit only browser and does not run Java.

Safari 10 (and later)Starting with Safari 10, the option to toggle 'Safe mode' still exists, but it is hidden.Now, when you go to set DBsign/Java to run in 'unsafe mode', the only options are 'Ask', 'Off', and 'On':However, if you press and hold the ' alt/option' key on your keyboard, you are given more options:Make sure that 'On' is checked, and 'Run in Safe Mode' is unchecked.If Java is working, and DBsign is able to load, you will see a page that looks like this:If the pages just sits there with a 'Loading DBsign.' message, then Java is probably not working properly. You should be able to change its settings now. You will most likely receive a DBsign error, but the web site should now be included in this list.

This can happen if your CAC certificates are either expired or revoked however, it is more likely that you either do not have CAC enabling software (or middleware) installed or it is not working properly. See the seciont above concerning Safari configuration.The 112 'no signing certificates' error usually means that DBsign was unable to find any usable certificates on your computer. If no error occurs, your page will look like this (with signature information filled out):If you get an error message when attempting to sign, please contact us for help.305 errors generally indicate that Safari has not been configured properly. This will tell DBsign to generate a digital signature using one of the certificates on your computer or smart card.

DBsign will not be able to use your CAC until this is working. This lets you know that the CAC software is installed and working. You should be able to pull your CAC out and your name will disappear from the list, and then plug it back in and your name will appear in the list again.

Configuring Java Db Serial Number Of

So, I tell people to remember the last 2 digits of the serial number of the cert that works and always use that one. This is not a DBsign thing, but it is some kind of incompatibility between OS X and the CAC. Can you login successfully with your CAC on those sites? Usually if that works, DBsign will work.If you are getting prompted to select between two certificates, then this might be because 1 of them usually does not work.

After you are logged back in, plug the reader back into the Mac and then put the card in the reader. But before you reboot, unplug your card reader from the Mac and also unplug the card from the reader. This actually does fix 139/132 problems sometimes and it's easy to do.

They conflict with each other and cause these symptoms.Try accessing some military CAC enabled websites such as web mail or portals. If it gets locked, you have to take it to an LRA or a badge office or something to get it unlocked.Sometimes these symptoms are caused by installing two different types of CAC software at the same time. Some users enter their OSX password here and end up locking their CAC card (3 failed PIN entry attempts will lock the card).

Also, Thursby PKard for about $30 is good and they offer excellent support.If you still need some help, please contact us. Uninstall them all, then install only one. Be sure and reboot the Mac after every install and uninstall. For instructions on uninstalling, see here. I would uninstall any and all CAC software that you installed and only install one. If not, then there seems to be an issue with your CAC software.

Configuring Java Db For Mac