User:Paulpehrson/Sandbox/Community Services Configuring the SSO Environment Simulator
Configuring the SSO Environment Simulator
As can be seen in Figure 2 by the arrows entering the green section from the browser and from the applications accessing the REST api, the simulator listens on two ports. One is known as the proxy port and is meant to simulate a next generation church site like labs.lds.org or beta.lds.org. Via configuration, traffic intended for applications under development and running on different ports on the local box is proxied to those other ports essentially mapping those applications into and making them appear as one seamless site. The second port has two purposes: it implements the REST api of the OpenSSO policy server for calls from applications and it provides a number of console pages. An example of the REST api usage is the sign-in application known as ml-auth used for labs and beta.lds.org. That application accepts user credentials, calls the REST api to start a session in the policy server and acquire the session token and SSO cookie name, then sets the SSO session cookie in the browser as it redirects to the originally targeted URL. Using the simulator’s REST implementation allows ml-auth to be developed and tested locally without a full OpenSSO environment. Before we show how such a set up is configured lets start with a more simple example that simply demonstrates the available console pages within the simulator.
Previous Page: SSO Environment Simulator
Next Page: Starting the Simulator