Skip to main content
Skip table of contents

Configure Guest Access - SuperWEB2

You may wish to allow users to access SuperWEB2 without logging in (referred to as guest access).

When guest access is enabled, users can access SuperWEB2 by clicking the guest login link on the login screen, or by visiting a special URL that bypasses the login screen altogether and takes them straight to SuperWEB2 (see below for more details).

Users logged in as a guest will not be able to save tables or custom data.

To allow guest access you need to:

  1. Create a dedicated guest user account.
  2. Configure SuperWEB2 to allow guest access using this account.

Step 1 - Create the Dedicated Guest User Account

By default SuperSTAR is supplied with a number of standard user accounts to enable you to complete the initial setup. One of the standard accounts is a guest user, so you may wish to use this for guest access.

Alternatively, you can create a new account for guest access in SuperADMIN, using the account command. For example:

CODE
> account createuser guestuser "Guest User Account" guestpassword

Once you have created the guest account, you must make sure that it has access to the appropriate databases. Learn more about configuring user permissions .

Step 2 - Configure SuperWEB2

To configure the guest user, you need to edit the following configuration file: <tomcat_home>\webapps\webapi\WEB-INF\web.xml

  1. Open the file in a text editor.

    Make a backup copy of this file before making any changes.

  2. Locate the following section:

    XML
        <!-- Guest user configuration -->
        <context-param>
            <description>
                This parameter defines the username to be used to connect to SuperADMIN for guest users
                It must be different to any username that has any other level of access.
            </description>
            <param-name>GuestUsername</param-name>
            <param-value>guest</param-value>
        </context-param>
        <context-param>
            <description>
               This parameter defines the password to be used to connect to SuperADMIN for guest users
            </description>
            <param-name>GuestPassword</param-name>
            <param-value>guestpassword</param-value>
        </context-param>
  3. Update the parameter values to the username and password of the guest user account. For example:

    XML
        <!-- Guest user configuration -->
        <context-param>
            <description>
                This parameter defines the username to be used to connect to SuperADMIN for guest users
                It must be different to any username that has any other level of access.
            </description>
            <param-name>GuestUsername</param-name>
            <param-value>guestuser</param-value>
        </context-param>
        <context-param>
            <description>
               This parameter defines the password to be used to connect to SuperADMIN for guest users
            </description>
            <param-name>GuestPassword</param-name>
            <param-value>guest</param-value>
        </context-param>
  4. Restart the Tomcat or SuperWEB2 service.
  5. Connect to SuperWEB2 in your browser and check that you can login as the guest user:

Allow Automatic Login as Guest

Once you have configured the guest login, you can allow users to log in as guest automatically by providing them with a special URL to access SuperWEB2.

Simply append /home to the standard SuperWEB2 URL, as follows:

If the SuperWEB2 URL is...The Automatic Guest Login URL is...
http://localhost:8080/webapi/http://localhost:8080/webapi/home

You can customise the display of the Guest log in link on the login screen. See these instructions for more details .

Prevent Guest Users from Creating Large Tables

If you decide to allow guest user access to your system, you may wish to prevent guest users from creating large tables. See Prevent Guest Users from Creating Large Tables - SuperWEB2 for more details.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.