Suppose you have a PowerServer Web application and another Web application (created using Visual Studio, COBOL, Web Services, SOA, etc.); and you want to access the PowerServer Web application from another Web application (suppose called ABC) without needing to log in again since you have already logged into the application ABC. In such a scenario, you can pass the user credentials to the PowerServer Web application without requiring re-login using either of the following two methods.
Method 1: Apply the command line argument.
PowerServer supports the CommandParm function and the command line argument in the Open event of a PowerBuilder application. These features can be applied for implementing single sign-on.
The command line argument can be passed to a PowerServer application in the following way:
http://192.0.1.94:8080/MyTest/index.html?user=appeon&password=appeon
This attaches the string "index.html?arguments" to the end of the original application URL ("index.html" must be included in the string).
If the user wants to launch a PowerServer application after logging on to another application (created using Visual Studio, COBOL, Web Services, SOA, etc.), the application passes the user information via the URL of the PowerServer application, and the user starts the PowerServer application without further login procedures.
It is also possible to pass the session ID only. A table is created in the database for keeping the session information of the application, with a session ID assigned to each session, and the session information containing user information. When the PowerServer application is launched with the session ID as its command line argument, the application reads from the database table the user information and authenticates the user. The user can start the PowerServer application without further login procedures.
Method 2: Use the single sign-on server to pass user information.
If you have set up the single sign-on server, you can take advantage of the single sign-on server to pass the user credentials. Normally the single sign-on server provides the authentication mechanism interface via Web service/EJB/JSP function etc. Make sure that your PowerBuilder can support the interface, then the PowerServer Web application should work with it.
