Atrium Sign On Page Modifications for Version 3.0.5

The Atrium sign on page has been modified in this release to better support tabbed browing and merged browser sessions.

Previously, Atrium would allow a user to come back to the sign on page in another browser window or tab while already signed into Atrium. The user (normally a developer would do this) could then sign in using different credentials. Due to the nature of tabbed browsing and merged browser sessions, this would cause all previous sessions to be "taken over" by the new credentials, causing some confusion for the user.

Starting with this release, the default Atrium sign on page will no longer allow this. It will detect previous sign on in the same browser session and redirect to Atrium automatically.

Developers who require the ability to run multiple concurrent sessions under separate user profiles can do so by using the browser's New Session option to obtain a new browser window that is not merged into a previous browser session.

To accommodate this new feature, some simple modifications have been made to the default Atrium sign on page. Users with customized pages should follow the instructions below to modify their pages.


  1. The <body> element used to call a function "init()" that was defined in the page like this:

    <body onload="init();">

    The page should now call the function "pui.signOnInit()", instead like this:

    <body "pui.signOnInit();">

    The init() function was used for setting focus to the first field on page load. This functionality is now performed in the new call. The init() function definition can be removed from the page, if desired.

    This new function call will check the signed in status on page load. If the user is already found to be signed in, he will be redirected to Atrium automatically.

  2. Add an id and non-display styling to the main content container. To do that, change:

    <div class="auth-box">


    <div class="auth-box" id="auth-box" style="display: none;">

    The non-display styling is used so that the form does not appear while the script is attempting to check if the user is signed in. This prevents screen "flash" if redirecting.

    The id is used for the script to get a reference to this content container. If found, the script will show the container (causing the form to appear), if it finds that the user needs to sign in.