Skip to navigation

Device login without a login form

Device login authenticates a whitelisted device identifier instead of asking the customer to type a license or username and password. You decide which identifier your integration uses, such as a processor ID or motherboard identifier, and add that exact value to the application’s Devices page.

Follow one workstation

You install MyApp on a customer’s workstation. The integration reads the motherboard identifier you selected. You create its device record, choose its plan, set its expiry and allow access. The next time MyApp opens, it reads the same identifier and asks AuthlyX to authenticate it.

Yes No Developer chooses motherboard orprocessor identification Read that identifier on thecustomer's workstation Whitelist the exact value inMyApp's Devices page Choose the device's plan, expiryand status Customer opens MyApp MyApp reads the same configuredidentifier SDK obtains a challenge andproves its installation key AuthlyX looks for a matchingdevice in this application Whitelisted, active and allowedby app policies? Issue a session tied to thatdevice and installation Reject login with a code and message MyApp uses the session forprotected requests Heartbeat checks whether accessis still valid

Match the identifier on both sides

A processor value in the whitelist will not match a motherboard value submitted by the app. Pick one strategy, use the same representation every time and test on the actual hardware you support. Do not randomly generate a new value at every launch.

The current V3 API field is called sid; it carries the configured identifier. The name of that field does not turn a Windows SID into a motherboard serial. The current SDK default on Windows reads the Windows account SID. Hardware-based device login therefore needs a supplied identifier through the SDK’s configuration. It is not automatic hardware discovery.

Keep exact configuration syntax in the language’s SDK reference. Do not use a SID-printing sample when your whitelist contains a processor or motherboard ID.

Device login and linked devices are different

A standalone device record is the identity used for device login. A linked device under a license or user records a device that used that license or username. Removing a linked device frees or resets that binding under the developer’s rules; it does not create a standalone device-login record.

When hardware changes

A replacement motherboard, a changed operating-system account or a new identifier strategy can produce a different value. Decide how you verify a replacement request and update the approved record. Do not automatically approve every unknown identifier: that removes the purpose of whitelisting.

Hardware identifiers are not passwords or cryptographic proof. Some are missing, duplicated or spoofable, especially on virtual machines. Installation signatures and server-side access checks remain necessary. Device login removes the typing step, not the need to check access.

Test before shipping

Whitelist a test identifier and confirm login succeeds. Try an unknown identifier and confirm rejection. Pause the device and check that its session stops working. Repeat after restoring it, and test the hardware-replacement process separately.