# Example 1 with an “implicit flow” with no code

This is simple integration for a CMS like Webflow or a Single Page Application in JS or a dApp. For this first example, you need the Altme Wallet and an Email Proof as a verifiable credential.

Later you could check the verifier data and change the parameters and landing page style in minutes on [https://talao.co](https://talao.co/). The example below is the verifier named “Example 1” in the select list. Make a copy of that verifier if you want to change the parameters.

So let’s try this verifier.

You can call it from a button link with a standard \<a href=…> balise or you can just copy this link in your browser :

<https://talao.co/sandbox/op/authorize?client_id=xgdfdbzwri&response_type=id_token&redirect_uri=https://altme.io>

Replace if needed the redirect\_uri argument by your own website.

You will be requested to present an email proof and then you will received an id\_token like that one below in your browser (id\_token=eyJhbGciO…..):

eyJhbGciOiJSUzI1NiIsImtpZCI6IjEyMyIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJ4Z2RmZGJ6d3JpIiwiZW1haWwiOiJ0aGllcnJ5QGFsdG1lLmlvIiwiZXhwIjoxNjY2MTk4M jczLjY2ODQ5MiwiaWF0IjoxNjY2MTk3MjczLjY2ODQ4NCwiaXNzIjoiaHR0cHM6Ly90YWxhby5jby9zYW5kYm94L29wIiwibm9uY2UiOm51bGwsInN1YiI6ImRpZDprZXk6ejZN a3R1d0x2U1VZZUplV0pnRHZKNlJmdFR2eVJTb05SR1h4Y2tlRTQ0cVRLa0tWIiwidXBkYXRlZF9hdCI6MTY2NTg0Mjc1MS4wfQ.MdWtxU8CjgSHfRgwUQWMMvhCLdgHzwQolWFwhtx -i3WJpZowwtpKSxh4smGPPhtBr4JPGYFAhjklZ2ojbW64VS8S07TNh3Q75TrgixAVguYnvsWCh5CLcxBRlcFW7iyWFm1WZ9VtNqXvlIL50tbfSQnpkcGVKbg2dmUKmuvUVDE1 qoJDedz7YKL3qWobkxzsrUlDGTKLvOHKdU3kaXnkGmiVxpZtwbIhE3pa27CjGFKAMX4rXOuiJ5N81LDX06GjV9KU4a4T5J2Bd2tgfvafjhJuTQD-1MaTWJMu\_ZTiHEjr4PTqYe\_C olYS2a\_Ougwk2FTQ6dKIQWClwhCZ-QfWuw

As you will see in an implicit flow, the id\_token is passed as a fragment (#), you can intercept it with JS in your page.

Copy this id\_token and go to [https://jwt.io](https://jwt.io/) , paste the id\_token value in the left side and you will get the following json data decrypted :

```
{
    "aud": "xgdfdbzwri",
    "email": "thierry@altme.io",
    "exp": 1666198273.668492,
    "iat": 1666197273.668484,
    "iss": "https://talao.co/sandbox/op",
    "nonce": null,
    "sub": "did:key:z6MktuwLvSUYeJeWJgDvJ6RftTvyRSoNRGXxckeE44qTKkKV",
    "updated_at": 1665842751
}
```

* “sub” is the subject ID, in our case it is the DID of the user (walletr Decentralized IDentifier). You can check that DID in your wallet settiongs !
* “aud” is the issuer URL in the OpenID format
* “email” is the main data of your verifiable credential

Based on that example you can request different types of credentials to authenticate your users as :

* Over 13
* Over 18
* Phone proof
* Gender proof
* Nationality proof
* Blockchain address
* ID card
* Custom credentials…

To make your own verifier, you just need to go to the plateform [https://talao.co](https://talao.co/) and to copy the example and configure the landing pasge.

More secured options are available with an OpenID authorization code flow.


---

# 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://altme-documentation.gitbook.io/altmes-documentation/altme-saas/openid-integration/example-1-with-an-implicit-flow-with-no-code.md?ask=<question>
```

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.