Status page authentication configuration

This Liberator configuration item enables you to define how access to Liberator’s status web page is authenticated.

These configuration items are available from Liberator 6.2.5

http-html-tokens

http-html-tokens allows you to change the authentication information that’s required for users to access the Liberator status page.

When you’ve installed a new Liberator and you access its status page from a web browser, you’re prompted for a username and password, which are, by default, admin and admin. You can change these user credentials using http-html-tokens. Alternatively, you can specify that Liberator should instead accept KeyMaster user credentials tokens to authenticate access to the status page.

Syntax: http-html-tokens <property> <value>

To configure page access by username and password, use property names status.username and status.password:

http-html-tokens status.username <username>
http-html-tokens status.password <password>

To configure page access by KeyMaster authentication token, use property names status.keymaster_url and status.keymaster_poll_url:

http-html-tokens status.keymaster_url <url-of-KeyMaster-servlet>
http-html-tokens status.keymaster_poll_url <url-of-KeyMaster-poll-servlet>

Type: array of strings

Default value: The following settings are defined by default:

http-html-tokens status.username admin
http-html-tokens status.password admin

These defaults define the same login credentials (username admin, password admin) that are built in to releases of Liberator prior to 6.2.5.

Changing the status page’s username and password

To change the username and password needed to log in to the Liberator status page, define the new credentials using status.username and status.password

For example:

http-html-tokens status.username guest
http-html-tokens status.password guest12345

Defining KeyMaster-based authentication

If you want to authenticate access to the status page through a user credentials token supplied by KeyMaster, first install KeyMaster, and then define the following settings for http-html-tokens

http-html-tokens status.keymaster_url "http://<myappserver>/servlet/StandardKeyMaster"
http-html-tokens status.keymaster_poll_url "http://<myappserver>/servlet/StandardKeyMaster/poll.jsp"

  • status.keymaster_url defines the URL of the KeyMaster servlet.

  • status.keymaster_poll_url defines the URL of the KeyMaster polling servlet.

    (When clients access Java-based KeyMaster through StreamLink JS, StreamLink accesses a servlet called Poll at regular intervals, so as to keep the session with the KeyMaster servlet alive.)

  • <myappserver> is a URL fragment specifying the web application server that hosts the KeyMaster servlets.

You must also configure the KeyMaster URL and KeyMaster poll URL in StreamLink: see the JSON configuration attributes keymaster_url and keymaster_poll_url in the StreamLink JS API documentation. These attributes are documented under the method caplin.streamlink.StreamLinkFactory.create(Map configuration).

See also: