Compliant Access via Session Key

Regulatory compliance may impose stringent data access requirements, such as having the user declare their intended use of the data, provide their IRB number and necessary PHI level, and sign associated terms of use documents every time they log in. This information is logged with each access of the data for later review or audit.

To enable programmatic use of data as if "attached" to a given session, an administrator can configure the server to allow the user to obtain a Session Key (or token) once they have logged in. This key can be used to authorize client code accessing LabKey Server using one of the LabKey Client APIs. Using any API key avoids copying and storing your credentials on the client machine. In the case of a session key, this access is tied to the current browser session and runs under the current context (e.g., your user, your authorizations and if applicable, your declared terms of use and PHI level, your current impersonation state, etc.) then expires at the end of the session, whether by timeout or explicit logout.

Enable Session Keys

  • Select (Admin) > Site > Admin Console.
  • Click the Admin Console Links tab.
  • Under Configuration, click Site Settings.
  • Under Configure API Keys, check the box for Allow Session Keys.
  • Click Save.

Access and Use a Session Key

Once enabled, the user can log in, providing all the necessary compliance information, then retrieve their unique session key from the username menu:

The session ID is a long, randomly generated token, beginning with the prefix "session|" that is valid for only this single browser session. Click Generate Session Key to see it; click Copy to Clipboard to grab it. Then click Done.

You can then paste this key into a script or other API access of data. Your use of the data will be logged with all the same data access information you provided when you logged in.

Example: R

For example, if you were accessing data via R, the following shows the usage:

labkey.setDefaults(apiKey="session|the_rest of the_long_string_session_id")

You will then be able to access the data from R until the session associated with that key is terminated, whether via timeout or log out.


Related Topics


Was this content helpful?

Log in or register an account to provide feedback

expand all collapse all