h1. Single sign-on from a "portal"
This is a single JSP that illustrates the type and complexity of code needed to have a portal (or other remote system) drive SGD.
The JSP
* creates an authenticated SGD session
* configures and starts the TCC
* launches an application
The simplest way to try this out is:
* download the JSP to /opt/tarantella/webserver/tomcat/5.0.28_axis1.2/webapps/sgd/singlesignon.jsp on an SGD server
* configure a DIFFERENT SGD server to accept third-party authentication
* edit singlesignon.jsp and change the hard-coded constants to point to the SGD server configured for third-party authentication
The first SGD server is effectively acting as a portal server remote from the second SGD server, and you get classpaths set-up for free!
This is very much a "proof-of-concept" and avoids issues like the security of trusted user credentials and other security measures like firewalls.
See attachments for source.
This is a single JSP that illustrates the type and complexity of code needed to have a portal (or other remote system) drive SGD.
The JSP
* creates an authenticated SGD session
* configures and starts the TCC
* launches an application
The simplest way to try this out is:
* download the JSP to /opt/tarantella/webserver/tomcat/5.0.28_axis1.2/webapps/sgd/singlesignon.jsp on an SGD server
* configure a DIFFERENT SGD server to accept third-party authentication
* edit singlesignon.jsp and change the hard-coded constants to point to the SGD server configured for third-party authentication
The first SGD server is effectively acting as a portal server remote from the second SGD server, and you get classpaths set-up for free!
This is very much a "proof-of-concept" and avoids issues like the security of trusted user credentials and other security measures like firewalls.
See attachments for source.