Skip to navigation

Sessions and heartbeats

A license login, from opening the app to signing out

Consider a customer opening MyApp on Windows. The app starts with its AppKey and version. Initialization returns application information and update settings. It does not authenticate the customer and does not grant access to protected app data.

The customer enters a license. Before submitting it, the SDK obtains a challenge using the installation’s public key. It signs the challenge with the private key kept on that installation. AuthlyX checks the license, application rules, expiry and device limits before issuing an authenticated session.

No Yes Yes Revoked or expired Network failure Customer opens MyApp Initialize using AppKey and app version Receive app settings and releaseinformation Customer chooses an enabledsign-in method License: submit the customer's key Username: submit username and password Device: submit the configuredwhitelisted identifier SDK obtains a challenge andsigns installation proof Does the identity pass accessand app-policy checks? X do Create server session tied toapp, identity and installation Return token, session ID,identity data and accessdeadline MyApp requests a variable,script, feature or otherprotected data SDK attaches token and signs theexact request Server validates session, proofand current access rules Return requested data when allowed Heartbeat runs at the configuredinterval Session still valid? Return renewed access deadline Stop protected actions and showthe reason Consider existing valid offlinepermission Customer signs out Revoke online session and clearlocal access

What the session contains

The server associates the session with the application, authenticated user/license/device, installation public key, device identifier, app version and expiry. A session ID identifies that record. The bearer token authorizes protected requests together with the installation proof; a session ID alone is not a replacement for these credentials.

The SDK stores the active session in its client instance. It adds the token and request proof when you read cloud variables, fetch scripts, read public metadata, send logs or use other protected endpoints. Direct HTTP clients must send the same documented authentication and signing fields themselves.

Why check again after login?

A customer can sign in at 9:00 and have their license paused at 9:05. Keeping the original login result forever would miss that change. A session check asks the server whether the linked identity, application and device are still allowed.

Use server heartbeat mode for automatic checks, or manual mode when your application schedules them. The server provides the interval; the configured fallback is ten minutes. An interval and an access deadline are different: permission is bounded by the deadline, not by a promise that the next network request will succeed.

When access ends

For a definitive ban, pause, expiry or ended session, stop protected actions and show a clear message. Keep unsaved work available where possible. The SDK must not terminate the process or choose a new screen for you. Your application decides whether to return to login or show a locked screen.

A timeout does not prove a ban. Handle connection failures separately and use offline access only when a valid permit allows it. After sleep or resume, recheck the session before resuming protected work. Logout ends the online session and clears local access state.

Test it

Sign in with a test license, check the session, then end it in the dashboard. Check again from the same running app. The old token must be rejected. Repeat with a paused license and with a network outage; those cases should produce different decisions.

See the SDK Check session page for language-specific calls and the Client API Sessions reference for direct requests.