Single Sign-on (SSO)
The Single Sign-On (SSO) functionality enables users to log into Hubble without being prompted for a username and password. Our products remember who the user is and automatically logs the user in.
SSO does not integrate with any outside directory access protocols such as LDAP or Active Directory. Our SSO functionality is self-contained and uses the user’s Windows Domain Name as an association to the Hubble user for logging into the product.
Enabling Single Sign-On (SSO)
Single Sign-On must first be activated in the Administrator application at the Repository level. Each Hubble user must also be enabled (this is enabled by default). Your Administrator can activate for your repository.
Enabling SSO at the repository is all you need enable this feature. The first time you log into Hubble, 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 SSO to function. Your Windows Domain Name has been associated to your Hubble username. Your Administrator can see this association using the Administrator application.
Now each subsequent login to Hubble will retain this association, thus automatically logging in the user. You will still need to select a Profile and/or Responsibility to complete the login; however you are no longer challenged for your username or password.
Possible SSO-related Errors when Logging In
If you have been set up by your Hubble Administrator to use Single Sign-On, there are a few reasons why you may be getting an error when logging into Hubble.
- If your user account is disabled, you will be prompted for your login credentials and SSO will NOT be in effect. Since you are disabled, you will be stopped from successfully logging in and an error will appear that your account has been disabled.
- SSO will fail if your Windows Domain Name is associated to more than one Hubble user such as in the example below:
The error will notify you of the users that share the same Windows Domain Name. such as in this example:
To disassociate the Windows Domain Name, your Administrator can right-click on the user (under Users & Groups) and select Disassociate Windows User:
- If you have SSO enabled and your password has expired, you will be notified at sign on that your password has expired and you are asked to change it.
You are notified that your last login did not require a password challenge, hence SSO is enabled. After completion of entering a new password, you are logged in successfully.
Miscellaneous Technical Information
Address Book Data Privacy Feature
The Address Book data privacy feature, available for JD Edwards E1 users, restricts users from viewing Address Book information that is determined to be personal data. When this is set up in E1, Hubble honors this and masks the information in inquiries.
When data is being masked in Hubble, the columns still display on the report but the data is masked. The data displays as **************** in the column if it is an alpha column, and 0 if the column is a numeric column.
There is not anything that you need to do in order to set up the Address Book data privacy feature in Hubble. As long as this is set up in E1, the same setup is honored in Hubble. (In E1, you must activate Personal Data Security as well as set up exactly what data you want to mask and which users or roles would see the masked data).
Rounding
After the data is returned from the database, amounts are rounded to the number of decimal places set in the formatting style being used. The default format style is set to 2 decimal places.
It is important to know that calculations are performed prior to formatting and is still using data from your ERP system. An export to Excel will typically show the "real" number.
Unicode Character Limitation
There are certain functions that will only allow English alphanumeric characters, including the following:
- Calculation names and captions
- Names of hierarchy nodes
- Names and descriptions in Budgeting