> For the complete documentation index, see [llms.txt](https://docs.oisy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oisy.com/introduction/internet-identity.md).

# Internet Identity

OISY Wallet uses Internet Identity for authentication.

<figure><img src="https://2757417719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEyGjMxMCIjbjm03hkdA%2Fuploads%2FMcTvAxojMYYZ8rMCdJOz%2FInternet%20Identity%20page.jpg?alt=media&amp;token=7ca743bf-e3bb-4511-a8df-f0457fc456d3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**OISY recently switched from version 1.0 of Internet Identity to version 2.0.**\
Please check [OISY Wallet switches to Internet Identity 2.0](https://docs.oisy.com/using-oisy-wallet/support/oisy-wallet-switches-to-internet-identity-2.0.md) for detailed information about this switch.
{% endhint %}

[Internet Identity](https://id.ai/) provides a secure, privacy-focused, and user-friendly authentication solution for the Internet Computer ecosystem. It allows users to securely and anonymously access decentralized applications (dapps) on the platform. Here are the key features of Internet Identity:

1. **Passwordless** Authentication: Instead of traditional usernames and passwords, Internet Identity uses passkeys, which are cryptographic public/private key pairs. Users can authenticate using biometric methods like fingerprint sensors (TouchID) or facial recognition (FaceID), or hardware security modules like YubiKeys or Ledger wallets.
2. **Privacy-Enhancing**: Internet Identity creates a unique pseudonym for each dapp a user authenticates with, preventing tracking across different applications and enhancing user privacy.
3. **Decentralized and Secure**: It operates entirely on the Internet Computer blockchain, allowing users to verify the code it runs. This decentralized approach enhances security and transparency.
4. **User-Friendly:** Users can create "identity anchors" and assign multiple devices to them, making it convenient to access dapps across different devices without managing complex cryptographic keys directly.
5. **No Personal Information Required:** Unlike traditional authentication methods, Internet Identity does not collect or store any personal identifying information from users.&#x20;
6. **WebAuthn Integration:** Internet Identity is built on the WebAuthn API, which is supported by modern web browsers and operating systems, ensuring broad compatibility.

More information:&#x20;

1. [Internet Identity Help & Support page](https://identitysupport.dfinity.org/) ↗
   1. [Internet Identity explained](https://identitysupport.dfinity.org/hc/articles/27213167791124-Internet-Computer-Internet-Identity) ↗
   2. [What's new in Internet Identity 2.0](https://identitysupport.dfinity.org/hc/articles/39593373981588-Internet-Identity-2-0) ↗
2. [Internet Identity homepage](https://id.ai/) ↗
3. [Manage your Internet Identity ](https://id.ai/manage)↗
4. [Manage your legacy Internet Identity (Internet Identity 1.0)](https://identity.internetcomputer.org/) ↗


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.oisy.com/introduction/internet-identity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
