Class: Keycard::Request::Attributes

Inherits:
Object
  • Object
show all
Defined in:
lib/keycard/request/attributes.rb

Overview

Base class for extracting attributes from a Rack request.

This provides the interface for attribute extraction, independent of how the application is served and accessed. It is not intended to be used directly; you should use AttributesFactory to create an appropriate subclass based on configuration.

The overall design is that a subclass will extract various attributes from the request headers and environment, and a set of attribute finders may be supplied to examine the base set and add additional attributes.

Constant Summary collapse

IDENTITY_ATTRS = 
%i[user_pid user_eid].freeze

Instance Method Summary collapse

Constructor Details

#initialize(request, finders: []) ⇒ Attributes

Returns a new instance of Attributes.



17
18
19
20
 
# File 'lib/keycard/request/attributes.rb', line 17

def initialize(request, finders: [])
  @request = request
  @finders = finders
end

Instance Method Details

#[](attr) ⇒ Object 



63
64
65
 
# File 'lib/keycard/request/attributes.rb', line 63

def [](attr)
  all[attr]
end

#all ⇒ Object 



67
68
69
 
# File 'lib/keycard/request/attributes.rb', line 67

def all
  base.merge!(external).delete_if { |_k, v| v.nil? || v == '' }
end

#base ⇒ Object

The set of base attributes for this request.

Subclasses should implement user_pid, user_eid, and client_ip and include them in the hash under those keys.



59
60
61
 
# File 'lib/keycard/request/attributes.rb', line 59

def base
  {}
end

#client_ip ⇒ Object

The user’s IP address.

This will be a string version of the IP address of the client, whether or not they have been proxied.



51
52
53
 
# File 'lib/keycard/request/attributes.rb', line 51

def client_ip
  nil
end

#external ⇒ Object 



71
72
73
74
75
 
# File 'lib/keycard/request/attributes.rb', line 71

def external
  finders
    .map        { |finder| finder.attributes_for(self) }
    .reduce({}) { |hash, attrs| hash.merge!(attrs) }
end

#identity ⇒ Object 



77
78
79
 
# File 'lib/keycard/request/attributes.rb', line 77

def identity
  all.select { |k, _v| identity_keys.include?(k.to_sym) }
end

#identity_keys ⇒ Object 



85
86
87
 
# File 'lib/keycard/request/attributes.rb', line 85

def identity_keys
  @identity_keys ||= IDENTITY_ATTRS + finders.map(&:identity_keys).flatten
end

#supplemental ⇒ Object 



81
82
83
 
# File 'lib/keycard/request/attributes.rb', line 81

def supplemental
  all.reject { |k, _v| identity_keys.include?(k.to_sym) }
end

#user_eid ⇒ Object

The user’s enterprise identifier.

If the client has authenticated as a user and the identity provider has releases one, this will be the “enterprise” identifier, some string that is useful for display and resolving to a person. It will tend to be something recognizable to that person, such as a network ID or email address. It may be helpful for displaying who is logged in or looking up directory information, for example. It should not be assumed to be permanent; that is, the EID may change for a person (and PID), so this should not used as a database key, for example.



43
44
45
 
# File 'lib/keycard/request/attributes.rb', line 43

def user_eid
  nil
end

#user_pid ⇒ Object

The user’s persistent identifier.

If the client has authenticated as a user, this will be a peristent identifier suitable as a key for an application account. It is expressly opaque, meaning that it cannot be assumed to be resolvable to a person or be useful for display purposes. It can be relied on to be stable for the same person as the identity provider determines that.



29
30
31
 
# File 'lib/keycard/request/attributes.rb', line 29

def user_pid
  nil
end