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

# Introduction to Auth

Introduction to authentication on Arweave

### Authentication on Arweave

To interact with applications, a user must be authenticated and the application in-turn must have permissions from the user to interact with the network on the users behalf. 

Additionally, every interaction (transaction) on the network has a unique signature. The signature is a hash of the various input parameters as well as the users key that helps authenticate the transaction and point it to a particular user.

### Authentication from a development perspective

Developers need to create user friendly tools and interfaces that verify user wallet connection to applications, use wallet addressed and request permissions from users to perform actions on their behalf.

### Libraries used

The functions associated with authentication leverage the following libraries:

* [ArConnect](https://github.com/arconnectio/ArConnect)
* [Othent](https://docs.othent.io/)

{% hint style="info" %}
Currently the library only supports the ArConnect extension for compatibility reasons. Support for additional browser based wallets will be added in the future.
{% endhint %}

### Auth based functions

In this section, we will look at the following features:

* connecting a web wallet
* disconnecting a web wallet
* getting address of connected web wallet
* getting permissions from user to use connected web wallet
* getting names associated with wallet addresses
* getting all addresses from web wallet extension
* getting a users active public key from web wallet
* checking if web wallet is installed
* connecting to applications using email ids
* disconnecting email ids from applications
* fetching user details of


---

# 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.arweavekit.com/auth/introduction-to-auth.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.