Common use of Licensor-Administered Authentication Clause in Contracts

Licensor-Administered Authentication. Where Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-campus IP address (thereby enabling access via username and password when logging in to a vendor website) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor-managed proxy prefix, Licensee nor any Participating institution will not be responsible nor liable for claims of breach or validity of such use.

Licensor-Administered Authentication. Where Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-campus IP address (thereby enabling access via username and password when logging in to a vendor website) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor-managed proxy prefix, Licensee nor any Participating institution will not be responsible nor liable for claims of breach or validity of such use.

Licensor-Administered Authentication. Where Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-on- campus IP address (thereby enabling access via username and password when logging in to a vendor website) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor-managed proxy prefix, Licensee nor any Participating institution Institution will not be responsible nor liable for claims of breach or validity of such use.

Licensor-Administered Authentication. Where Licensor provides alternative methods of access and authentication beyond the Licensee-Licensee- administered methods described herein, e.g. by allowing users to establish a personal login from an on-campus IP address (thereby enabling access via username and password when logging in to a vendor website) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor-managed proxy prefix, Licensee nor any Participating institution will not be responsible nor liable for claims of breach or validity of such use.