Document activity_who and related options for SIP user activity tracking

Bug #1736173 reported by Jeff Godin on 2017-12-04
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Jeff Godin

Bug Description

Commit aebf4a5 in 2012 introduced support for SIP actions to generate user activity records.

With this support came new configuration options for the SIPServer config file:

activity_who (associated with <login> or <institution>)

default_activity and force_activity_who (associated with <implementation_config>)

This feature and these options appear to have no current documentation.

Jeff Godin (jgodin) on 2017-12-04
Changed in evergreen:
assignee: nobody → Jeff Godin (jgodin)
Revision history for this message
Michele Morgan (mmorgan) wrote :

Adding a link to an IRC discussion for those seeking more information:

As an example, we set up an activity type to track OverDrive logins using SIP authentication.

In oils_sip.xml:

<login id="overdrive" password="<REDACTED>" activity_who="overdrive" institution="noble"/>

Pertinent values in config.usr_activity_type:

ewho: overdrive
ewhat: verify
ehow: sip2
label: OverDrive Login

Changed in evergreen:
status: New → Confirmed
Jane Sandberg (sandbej) on 2018-02-19
tags: added: sip
removed: sip2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers