# Device Authenticator
Device Authenticator uses the `SystemInfo.deviceUniqueIdentifier` to identify the client.
For platforms that don't support `deviceUniqueIdentifier` a GUID is generated and stored in `PlayerPrefs`.
{% hint style="warning" %}
NOTE: deviceUniqueIdentifier can be spoofed, so there's no guarantee of security.
{% endhint %}
* Drag the Device Authenticator script to the inspector of the object in your scene that has Network Manager
* The Device Authenticator component will automatically be assigned to the Authenticator field in Network Manager
When you're done, it should look like this:
{% hint style="info" %}
You don't need to assign anything to the event lists unless you want to subscribe to the events in your own code for your own purposes. Mirror has internal listeners for both events.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://mirror-networking.gitbook.io/docs/manual/components/network-authenticators/device-authenticator.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
