This is the documentation for SuperSTAR 9.8

SuperSTAR 9.9 is now available.
View this page in the SuperSTAR 9.9 documentation or visit the SuperSTAR 9.9 documentation home.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

By default, guest access is enabled and is configured to use this account for guest access.

Note
iconfalse

If you decide to keep guest access enabled on your deployment and use the default guest user account, then you are recommended to change the password for this account.

Configure Guest Access

If you want to use a different user account for guest access, you will need to complete the following configuration steps:

...

  1. Open <tomcat_home>\webapps\webapi\login.xhtml in a text editor.
    Str_takebackup
  2. Locate the following section:

    Code Block
    languagexml
    <tr class="loginForm-buttons">
        
    <td class="leftCol">
            <h:commandLink value="#{messages['page.login.guest.login.text']}" tabindex="0"
                           action="#{loginBean.authenticateGuest}" styleClass="guestLoginLink"/>
        </td>
        
    <td class="rightCol rightAlign">
            <h:commandButton id="login2" value="#{messages['page.login.login.button.label']}" tabindex="0"
                             action="#{loginBean.authenticate}" styleClass="activeButton"/>
        </td>
    </tr>
  3. Comment out the element that prints the guest login link:

    Code Block
    languagexml
    <tr class="loginForm-buttons">
        
    <td class="leftCol">
            <!-- <h:commandLink value="#{messages['page.login.guest.login.text']}" tabindex="0"
                           action="#{loginBean.authenticateGuest}" styleClass="guestLoginLink"/> -->
        </td>
        
    <td class="rightCol rightAlign">
            <h:commandButton id="login2" value="#{messages['page.login.login.button.label']}" tabindex="0"
                             action="#{loginBean.authenticate}" styleClass="activeButton"/>
        </td>
    </tr>
  4. Save your changes to the file.
  5. Open <tomcat_home>\webapps\webapi\WEB-INF\web.xml in a text editor and check the GuestUsername parameter to confirm which account is currently configured for guest access:

    Code Block
    languagexml
        <!-- 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>

    In this example, the account with the username guest is configured for guest access.

  6. Leave the settings in web.xml unchanged, but go to SuperADMIN and delete this guest user account. For example:

    Code Block
    > account guest remove

    This step is necessary in order to prevent users from logging in using the special /home URL (see below).

  7. Restart Tomcat or the SuperWEB2 service.

...