SSO Simulator Sign-In Pages
The simulator provides three pages that can be used to sign-in users when enforcing access to URLs as declared in the configuration file. These all reside under the console port path of “/admin/”. They are explained in the table below. When using the openSSO rest API an alternative approach was that an application could provide its own sign-in page and leverage the openSSO REST api to initiate sessions and that application page could set the cookie itself. The sign-in page for beta.lds.org was developed in this manner using the simulator and mapping its sign-in page into the site via unenforced URLs as outlined in the section on the <unenforced> element.
|selectUser.jsp||This page includes a list of current sessions allowing you to change between sessions to test for session crossover issues in an application. If a goto query parameter is specified it will automatically redirect there after a user is selected. Users listed are those defined in the configuration file. Arrows to the left of users and sessions indicate which session for which user is currently the active one in the browser.|
|simpleSelectUser.jsp||This page is a simplified version of the selectUser.jsp page only showing the list of users that can be selected to start a session. Like its more complex version if a goto query parameter is specified it will automatically redirect there after a user is selected. Users listed are those defined in the configuration file. Arrows to the left of a user indicates that the cookie in the browser is for that user.|
|codaUserSelect.jsp||This page is specifically intended for use when the <users> element declares its optional source element. This page enables entering usernames from the external Coda service and the simulator will create that user if they are not already defined in the config file and import that user’s attributes. Thereafter, the user will appear as a link for a shortcut to start another session for that user. Once the simulator is restarted these loaded users are no longer available and must be loaded again. If such users are defined in the config file their links will always be shown but their attributes loaded from Coda. If not found in Coda then any locally defined attributes will be used. ie: Coda attributes if found take precedence.|