ResourceAuthenticationEvents
URL/api/v2/authentication_events
Supported Standard Operations
  • View (all)

Attributes

See authentication_events for definitions of attributes.

Sample Record

{
  "id": 3274,
  "authenticated_identifier": "sobu",
  "authentication_event": "IN",
  "remote_ip": "10.211.55.2"
}

Supported Filters

View (all)

Additional filters:

  • authenticated_identifier

Example: Obtain Authentication Events for a given Authenticated Identifier

GET /registry/api/v2/authenticated_events?authenticated_identifier=c29idQ--

Implementation Notes

View (all)

In order to work with identifiers that contain HTTP reserved characters, authenticated_identifier must be encoded using base64 encoding. However, because base64 encoding can itself result in special characters, these are further mapped as follows:

  • + (plus) is replaced with . (dot)
  • / (slash) is replaced with _ (underscore)
  • = (equals) is replaced with - (dash)

Applications such as plugins using the Registry codebase can use \App\Lib\Util\StringUtilities::urlbase64encode() to encode identifiers.

View (all)

Authentication Events are tracked by authenticated identifiers, and therefore are not bound to any specific CO. A Privileged CO API User may retrieve all Authentication Events associated with any authenticated (login) Identifier associated with any Person within its CO, even if the Authentication Event was intended for access to another CO. (AR-AuthenticationEvent-3)

The authenticated_identifier filter is required for Privileged CO API Users. Only one value is supported per GET request.

  • No labels