Integration · Authentication

CAS authentication for campus parcel lockers

CAS is still widely deployed at universities and works well for kiosk-style logins. We support the CAS 3.x protocol with attribute release.

Request a demoDownload RFP template →

Data Sync

What data flows through this integration

Fields synced

  • →Username (NetID)
  • →Attributes via CAS 3.x ticket validation

Authentication

CAS 3.x service ticket validation; we act as a registered CAS client.

Supported versions

  • · Apereo CAS 5.x and later

Setup

How a deployment goes

01

Register service

Your CAS admin registers the locker software as a CAS service.

02

Attribute release

Configure required attributes (NetID, affiliation) for release.

03

Test

Test ticket validation with a sample student account.

04

Go live

Enable CAS authentication at kiosks and admin tools.

Frequently asked questions

FERPA-aligned by design

All integrations follow minimum-necessary data practice, with auditable access logs and configurable retention.

Read FERPA posture →

Need an RFP starter?

Download our higher-ed RFP template with placeholder fields for technical specs, security, integration, SLA, and pricing.

Get the RFP template →