Skip to main content

Set Up Desktop Simplified Sign-On

Overview

Desktop Simplified Sign-On functionality enables users to log into the product without being prompted for a username and password. Our products remember who the user is and automatically logs the user in.

Desktop Simplified Sign-On does not integrate with any outside directory access protocols such as LDAP or Active Directory. Our Desktop Simplified Sign-On functionality is self-contained and uses the user’s Windows Domain Name as an association to the Hubble user for logging into the product.

Note: The Desktop Simplified Sign-On facility is distinct from the Web Single Sign-On (SSO) facility. The Web SSO facility is used to simplify access to content for Hubble Web users and to streamline user administration. Web SSO uses the SAML 2.0 standard and an existing SAML ID provider. Refer to the Configuring Single Sign-On with SAML topic in the Hubble Initial Deployment Guide for details.

Desktop Simplified Sign-On in JD Edwards World environments - Desktop Simplified Sign-On only works for a JD Edwards World environment when World/AS400 interactive authentication is not required. This is determined in Administrator within the Connection Settings for the specific Profile being used. These Connection Settings allow you to select which security authentication mode you want your users to use as part of the login process.

The Connection Settings are in the World Security Options screen within the Profile wizard. Only option 4 (system credentials) can be used with Desktop Simplified Sign-On. Options 1, 2 and 3 are mutually exclusive with Desktop Simplified Sign-On because these options require Hubble to get a password from the user upon logging into their Hubble product.

Enable Desktop Simplified Sign-On

Desktop Simplified Sign-On must first be activated in Administrator at the Repository level. Each Hubble user must also be enabled (this is enabled by default). There are two ways you can activate Desktop Simplified Sign-On for your repository:

  1. Use the Install Setup Wizard to create a new Repository and check the Desktop Simplified Sign- On checkbox as shown below:

  2. Edit your existing Repository. Right-click on your repository after logging into it, click Edit to open the Repository Properties dialog, and then check the Desktop Simplified Sign-On checkbox as shown below:

Enabling Desktop Simplified Sign-On at the repository is all you need enable this feature. The first time you log into your Hubble product, you will be prompted to key in your username and password information. Once successfully logged in for the first time, you have now defined the association required for Desktop Simplified Sign-On to function. The user’s Windows Domain Name has been associated to their Hubble Username. Your administrator can see this association using the

Administrator application. Below you can see that the User DEMO is now associated to the Windows Domain Name of INSIGHTSOFTWARE\cstern:

Now each subsequent login to the application will retain this association, thus automatically logging in the user. The user may still need to select a Profile and/or Responsibility to complete the login; however they are no longer challenged for their Username or Password. The user will still need to select their Profile and/or Responsibility in the login dialog.

Activate Desktop Simplified Sign-On at User Level

Desktop Simplified Sign-On is activated at the user level by default. All users are automatically enabled for Desktop Simplified Sign-On by default when:

  • Creating new users
  • Synchronizing in users from the ERP Profile
  • Restoring users from a previous backup

In Administrator, you can see this by editing any user. The checkbox for Allow Desktop Simplified Sign- On for this user will be selected.

Desktop Simplified Sign-On and Password Policy

With Desktop Simplified Sign-On switched on, the Hubble passwords in the Object Repository are not needed and not asked for as long as Desktop Simplified Sign-On is operating for the user.

This means that if, for example, you have Hubble’s Password Policy set for a user's password to expire in 90 days, technically at 90 days the password in the repository is marked as expired. However this does not impact the user because the Hubble password in the repository is not being used. As long as Desktop Simplified Sign-On continues to operate, the user will never know that his/her password has expired.

If for some reason, at some point, Desktop Simplified Sign-On stops operating (switched off, or more than one Hubble account is associated with the same Windows domain account), then the application will ask the user for his/her username and password. If the password has expired, then the process will be the same as before we had Desktop Simplified Sign-On: the user needs to enter his/her old, expired Hubble password and choose a new one.