Secure Global Desktop 5.1 Tomcat 403 Error After Manually Moving A Session From /sgd To /sgd/mydesktop (Doc ID 1926738.1)

Last updated on JULY 12, 2016

Applies to:

Oracle Secure Global Desktop - Version 5.1 to 5.1 [Release 5.0]
Information in this document applies to any platform.

Symptoms

When using Secure Global Desktop (SGD) 5.1, users were able to login to their Webtop/Workspace and open a new tab to initiate a Mydesktop launch of their session. Since upgrading to 5.1, the launch has been failing. Specifically, once logged into the SGD session with the   http://servername/sgd  URL, and then opening another tab in the browser and go to http://servername/sgd/mydesktop,  you get an Tomcat 403 error:

HTTP Status 403 -


type Status report

message

description Access to the specified resource has been forbidden.


Apache Tomcat/7.0.54

 

You also get this error if you login to  http://servename/sgd and change the browser URL to  http://servename/sgd/mydesktop

NOTE: These modes of operation are uncommon but supported. The default way to login and launch applications are outlined in the SGD User Guide at:

http://docs.oracle.com/cd/E41492_01/E41494/html/index.html

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms