How does the SafeStick to SafeConsole Registration process work?

02 Sep 2010

Support Center » Knowledgebase » How does the SafeStick to SafeConsole Registration process work?

	How does the SafeStick to SafeConsole Registration process work?

Solution SafeConsole uses certificates to create the trust between it and the SafeSticks registered to it.

When you first install SafeConsole you are invited to create or import a certificate for it use - along with the hostname/fqdn that it will respond to.

Once complete, you must install this certificate into the Trusted Root Certification Authorities certificate store on the SafeConsole server - this way the Apache server running SafeConsole and browser match.

The next step is to deploy the same certificate down to the desktops so that the desktop and server can talk to each other using the "Certificate-based trust" that has effectively been established. The final part of the deployment is that of a single registry key that must exist on the desktops in the following format:

https://exactandfullhostnameusedincertificate/safestick

Under:

HKEY_CURRENT_USER\Software\BlockMaster\SafeStick

Make sure that the SafeStick firmware is 3.0 and above as well. ("SafeConsole aware")

This will be all you need to do to allow your SafeSticks to then prompt you to register a SafeStick against the logged-on user.

Some important notes follow:

The certificates MUST match in three places:

1.) The desktop (Trusted Root Certification Authorities certificate store)
2.) The SafeConsole server (Trusted Root Certification Authorities certificate store)
3.) The SafeConsole configuration wizard (Apache)

Even a brand new SafeStick will not prompt if there is any mis-match.

But otherwise, it will prompt straight away if the right cert and registry key are in place - the SafeStick.exe software is hard-coded to look for the presence of this registry key and then use the URL contained to "find" the SafeConsole server - then it checks that there is a certificate based-trust established between the SafeConsole and the desktop via their cert stores - assuming these two match what Apache (SafeConsole) itself is using (configuration wizard) then it will prompt for registration of the SafeStick to be tied to the locally logged on user, picking up the user name, OU and SafeStick serial number.

We hope this clarifies how this process works.

Article Details

Article ID:

580

Created On:

08 Oct 2009 01:09 PM