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

# Meeco authentication

This doc presents the step-by-step of how to configure the Guardian application to allow authentication via the Meeco Wallet

At the end of this doc, this is what suppose to see in the Guardian app.

<figure><img src="https://content.gitbook.com/content/VEIy5NWArZNH7ps6ViQU/blobs/WSW4av0EUKAYBgfTMvmT/Screenshot%202023-08-02%20at%2020.23.36.png" alt=""><figcaption></figcaption></figure>

### Meeco credentials

Be sure to configure your Meeco credentials in `configs/.env.develop.guardian.system`

```
MEECO_AUTH_PROVIDER_ACTIVE=1
MEECO_BASE_URL=https://api-sandbox.svx.exchange
MEECO_OAUTH_URL="https://login-sandbox.securevalueexchange.com/oauth2/token"
MEECO_OAUTH_CLIENT_ID=571*********************e6a
MEECO_OAUTH_SECRET_ID=ONO@*****************rnNxpNt
MEECO_OAUTH_SCOPE=openid
MEECO_OAUTH_GRANT_TYPE=client_credentials
MEECO_ORGANIZATION_ID="09f7115e***********be032d6ca149"
MEECO_PASSPHRASE=7MHHMTJQQ******************7TPBH2P71XKDH1ZPF
MEECO_ISSUER_ORGANIZATION_ID="did:web:did-web.securevalue.exchange:343b08f3-***********-3f2d8a146a0d"
MEECO_ISSUER_ORGANIZATION_NAME=
MEECO_PRESENTATION_DEFINITION_ID="832e996c-**********-9d170fa381a8"
```

You might find the values in the portal <https://portal.securevalueexchange.com/>

### Where to find these credentials?

The very first thing is to activate the use of Meeco provider

```
MEECO_AUTH_PROVIDER_ACTIVE=1
```

For the `MEECO_OAUTH_CLIENT_ID` and MEECO\_OAUTH\_SECRET\_ID check the page below:

<figure><img src="https://content.gitbook.com/content/VEIy5NWArZNH7ps6ViQU/blobs/0SmEeXGOY0jsnHl62qGk/Screenshot%202023-08-02%20at%2020.44.38.png" alt=""><figcaption></figcaption></figure>

For the variables: `MEECO_OAUTH_SCOPE=openid` and `MEECO_OAUTH_GRANT_TYPE=client_credentials` keep it as it is.

The MEECO\_ORGANIZATION\_ID variable value can be found here

<figure><img src="https://content.gitbook.com/content/VEIy5NWArZNH7ps6ViQU/blobs/jw6xuRdXGpGSDWJ2NFlr/Screenshot%202023-08-02%20at%2020.49.20.png" alt=""><figcaption><p>Account settings</p></figcaption></figure>

The `MEECO_ISSUER_ORGANIZATION_ID` and `MEECO_ISSUER_ORGANIZATION_NAME` value are found on the page below

<figure><img src="https://content.gitbook.com/content/VEIy5NWArZNH7ps6ViQU/blobs/j4aCjUk9AbtDG17ILKo4/Screenshot%202023-08-02%20at%2020.53.58.png" alt=""><figcaption></figcaption></figure>

Finally, the `MEECO_PRESENTATION_DEFINITION_ID` value is found here

<figure><img src="https://content.gitbook.com/content/VEIy5NWArZNH7ps6ViQU/blobs/Afk0V6cpItFGOP7XJp0R/Screenshot%202023-08-02%20at%2020.59.02.png" alt=""><figcaption></figcaption></figure>

Once the env variables are defined you have to turn it on on the frontend. Set true the attribute **`isMeecoConfigured`** on the folder`frontend/src/environments/environment.ts`

<figure><img src="https://content.gitbook.com/content/VEIy5NWArZNH7ps6ViQU/blobs/TjNx9swczZ6fAdoMSAi8/Screenshot%202023-08-02%20at%2019.43.11.png" alt=""><figcaption></figcaption></figure>

Note that there are at least three different environment files: `environment.prod.ts`, `environment.demo.ts` (e.g) change them according to your configurations.

Be sure to run the `docker-compose up --build` (e.g) command again to have it done.\\

So, enjoy your new authentication mechanism.


---

# 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://guardian.hedera.com/docs/3.6.0/guardian/readme/security-1.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.