Installation guide

14021467 – Webtop Language Selection Issue

• Import the web services SSL certificate for each Oracle VDI host into the certificate truststore on each

SGD server. Depending on your configuration, the truststore is either the CA certificate truststore or a

dedicated truststore.

• Reconfigure the VDI broker to use the host names that appear in the web services SSL certificates.

Change the preferredhosts and failoverhosts settings to use the new host names.

3.1.18. 14021467 – Webtop Language Selection Issue

Problem: Typically, users can select a preferred language from the list on the SGD Welcome Page. They

then click Log in to access a webtop in that language.

After selecting a language at the SGD Welcome Page, users may not be able to select a different language

for subsequent logins.

Cause: A known issue with caching of the preferred language selection.

Solution: Use one of the following workarounds:

• Clear your browser cache before selecting a different language.

• Locate the following text, at line 66 in the localeutils.jsp file:

prefLang = (String) pageContext.getAttribute(PREF_LANG, PageContext.SESSION_SCOPE);

The localeutils.jsp file is in the /opt/tarantella/webserver/tomcat/tomcat-version/

webapps/sgd/resources/jsp directory on the SGD server.

• Edit the file, to read as follows:

if (httpServletRequest.getParameter(LANG_SELECTED) == null)

prefLang = (String) pageContext.getAttribute(PREF_LANG, PageContext.SESSION_SCOPE);

3.1.19. 14085800 – Active Directory Aged Password Handling Issue

Problem: Following expiry of their Active Directory password, users are able to update their password

when prompted by SGD. However, the updated password is not always stored correctly in the password

cache.

This means that some users might be prompted for authentication credentials every time that they start an

application hosted on a Windows application server.

The issue is seen when the following are true:

• SGD is configured to automatically try the user's password when logging in to an application server, if

the password has been cached. SGD does this by default.

• The Active Directory service object has the password expiry setting (--check-pwd-policy) enabled.

Cause: A known issue with how SGD handles aged passwords for Active Directory.

Solution: Use the following workaround.

• Disable the password expiry feature for the service object. For example:

$ tarantella service edit --name ad1-east --check-pwd-policy 0

• Configure the Domain Name attribute for the Windows application object. For example: