CampusLayer Connect
Connect school systems without replacing them first.
Connect is the first working layer of CampusLayer. Canvas is being connected through user supplied access tokens today. Skyward uses the compatibility connector path while CampusLayer Desktop is built to handle its local session and SSO requirements.
Provider connections
Connect and verify provider accounts from one CampusLayer account.
Encrypted credentials
Provider secrets are encrypted server side before they are stored.
Live verification
CampusLayer tests the provider credential before marking a connection active.
Desktop next
CampusLayer Desktop will provide the local runtime needed by providers such as Skyward.
Canvas now
URL, access token, verify, connect.
A user provides the Canvas URL and access token from their own Canvas account. CampusLayer verifies that token against Canvas, encrypts it, and can immediately use it for live authorized API requests.
Skyward next
Put the local session work inside CampusLayer Desktop.
The existing Skyward connector remains useful. CampusLayer Desktop is the piece that will manage local SSO and session state without asking the user to manually operate a reverse tunnel.