Student device login and Secondary authentication

Dyknow identifies each student user for monitoring by matching their device login to their Dyknow student User profile.

There's no need to manage MAC addresses or machine-specific information. 

Schools should follow our Import Manager process to send the following roster data to Dyknow via direct API integration or via FTP with .csv files:

  1. Users
  2. Classes
  3. Enrollments 



The Dyknow Cloud Connector identifies the student differently depending on the OS.

For student Windows and Mac devices:

  • Dyknow silently identifies the user at OS login by matching credentials against DITO, which occurs regardless of domain status or use of third-party user authentication tools (e.g. AD, OD, LDAP, etc.).

  • Students using Windows/PC devices and Mac devices must login to their device with the same Username that's recorded in Dyknow in order to be identified for monitoring.

  • To identify login credentials on a student Windows/PC device:
    • Open File Explorer
    • Click the OS (C:) file path
    • Click the Users file
    • Review the list of file names/usernames to identify the correct student device username (note: there may also be a Default username and a Public username listed)
  • To identify login credentials on a student Mac device:
    • Navigate to Settings > Users & Groups > Login Options
    • Identify the "Account Name" (this must match the Dyknow Username)

For student Chromebook devices:

  • Students using Chromebook devices must login to their device with the same Email Address that's recorded in Dyknow in order to be identified for monitoring.

  • To identify the email address associated with a student Chromebook device login:
    • Open Chromebook System Preferences
    • Scroll down to the People section
    • Locate the name of the student in question, and identify the email address associated



Instead of automatically pulling the user a student is logged into a device as, secondary authentication prompts you to identify which user to login to Dyknow.

Secondary authentication...

  • Is required when the student's Dyknow username/email address doesn't match that which student used to login to their device;
  • Is ideal for schools with BYOD environments; and,
  • Must be enabled, per device OS, by the Dyknow Service Team in :: Admin Settings :: Deployment Groups.

Students will be prompted with the Dyknow secondary authentication window anytime they login to their device (after logging off, restarting, etc.). Student passwords do not matter! Students could enter anything for their password and they would still be logged into Dyknow.

For student Windows and Mac devices:

  • When the OS login credentials don't match our records, the Dyknow login dialog box appears on the student device asking for "username and password."
  • Once the student enters her/his credentials that match our Dyknow records, the system knows her/him and the credentials are cached.
  • Even if a student clicks the “X” icon to close out the secondary authentication window, it only disappears from the screen for a second before popping back up.
  • If a student moves the secondary authentication window to "hide" it, an easy way to find the “hidden” secondary authentication window is to right-click on the desktop > click Display Settings > select 100% in the Scale and Layout section. This will “zoom out” your view of the desktop, enabling you to see that “hidden” secondary authentication window.



For student Chromebook devices:

  • This dialog is the default action and will similarly be cached, then the student will be prompted to "Share Screen."
Was this article helpful?
2 out of 6 found this helpful
Have more questions?
Submit a request



Article is closed for comments.

Articles in this section

See more