diff --git a/docs/proxy/description.md b/docs/proxy/description.md
index b116902317fc40c8ebffeb6262befb8b6b3bdbc8..7a7caae185d250b647e7730b1369bcdb80070109 100644
--- a/docs/proxy/description.md
+++ b/docs/proxy/description.md
@@ -1,17 +1,17 @@
 !!! warning ""
     :construction: Section under Construction :construction:
 
-This section of documentation refers to the Enedis Oauth protocol working hand in hand with our custom proxy and the cozy-stack.
-To fully understand its whereabouts, you should also look at the [enedis konnector](./konnectors/enedis.md) documentation.
+This section of documentation refers to the Oauth protocols working hand in hand with our custom proxy and the cozy-stack.
+To fully understand its whereabouts, you should also look at the [enedis konnector](../konnectors/enedis.md) and [grdf konnector](../konnectors/grdf.md) documentation.
 
 !!! info "proxy code source"
     Feel free to check the proxy [code](https://forge.grandlyon.com/pocs/cozy/cozy-oauth-proxy) at all time when reading this documentation.
 
 ## Oauth Dance
 
-In order to access customer data from Ecolyo, one must first obtain customer authorization. This authorization is materialized by an access token and it must be obtained by the Authorization API exposed by Enedis.
+In order for Ecolyo to access customer data, one must first obtain customer authorization. This authorization is materialized by an access token and it must be obtained by the APIs exposed by each energy providers.
 
-The API is implemented on Oauth 2.0 protocol, it requires authentication from the customer along with its given consent.
+These APIs implement Oauth 2.0 protocol, it requires authentication from the customer along with its given consent.
 
 ### Enedis Data Connect
 
@@ -30,7 +30,7 @@ Regarding Enedis, two endpoints are exposed:
   </colgroup>
   <thead>
     <tr class="header">
-      <th>Name</th>
+      <th>Paramater</th>
       <th>Description</th>
     </tr>
   </thead>
@@ -66,7 +66,7 @@ Regarding Enedis, two endpoints are exposed:
   </colgroup>
   <thead>
     <tr class="header">
-      <th>Name</th>
+      <th>Paramater</th>
       <th>Description</th>
     </tr>
   </thead>
@@ -104,6 +104,10 @@ Regarding Enedis, two endpoints are exposed:
 
 On success, response will contain **access_token** or **refresh_token**, **usage_point_id** among other things. All informations will be stored by the cozy-stack in a cozy-accounts database.
 
+### Grdf Adict
+
+#### /access_token
+
 ### Cozy Oauth Protocol
 
 !!! info "cozy oauth flow documentation" 
@@ -111,10 +115,10 @@ On success, response will contain **access_token** or **refresh_token**, **usage
 
 #### Couchdb
 
-It is necessary to add in a couchdb database all informations needed for the konnector authentication to work properly.
+The couchdb database must hold all informations needed for the konnector authentication to work properly.
 
 Auth informations are stored in the **secrets/io-cozy-account_types** database.
-You can create manually the document by entering these parameters:
+You can create manually the document by entering these parameters for each konnector:
 
 <table>
   <colgroup>
@@ -167,23 +171,34 @@ If the token request is a success. An account/service-name database will be adde
 
 ### Why we Need a Proxy
 
-The Oauth dance could be easily wrapped up with the two requests seen above. But since Ecolyo is an application hosted on multiple personnal cloud, following this guideline would mean that we need a **client_id** and a **client_secret** for each one of all the applications running.
+The Oauth dance could be easily wrapped up with the two requests seen above. But since Ecolyo is an application hosted on multiple personnal clouds, following this guideline would mean that we need a **client_id** and a **client_secret** for each one of all the applications running.
+
+To answer this issue, two solutions are possible depending on what the energy supplier is willing to do.
+
+- Providers could allow wildcard subdomains when registering the callback URI, it would parse the subdomain and adapt its redirection when answering **/auth** call.
+
+Exemple:
+
+    https//*.cozygrandlyon.cloud/account/redirect -> parse subdomain before .cozy
 
-To answer this problem, it was decided to run a proxy as a middleware that would provide a generic endpoint to cater for all Oauth2 redirections and redirect to the stack that was originally calling the protocol.
+    xyz.cozygrandlyon.cloud/account/redirect -> redirect to xyz
+    toto.cozygrandlyon.cloud/account/redirect -> redirect to toto
+
+- If the provider (Enedis for instance) is not accepting wildcards, then we put a proxy as a middleware to provide a generic endpoint to cater for all Oauth2 redirections. 
 
 #### Result
 
-Henceforth the proxy is now the one calling the auth and token endpoints. It's also the proxy that is registered as redirect_uri.
+With that in mind, the proxy is now the one calling the auth and token provider endpoints. The instance name will be contained in redirect_uri, the stack will insert this parameters by itself in the /auth call.
 
 3 endpoints are created in the proxy:
 
-- One for the auth (called by the cozy-stack)
-- One for the token (also called by the cozy-stack)
-- One for the redirect_uri (called by the service provider, Enedis)
+- One for the auth
+- One for the token
+- One for the redirect
 
 #### Proxy flow
 
-stack -> proxy/auth -> enedis/auth -> proxy/redirect -> stack -> proxy/token -> enedis/token
+stack -> proxy/auth -> provider/auth -> proxy/redirect -> stack -> proxy/token -> provider/token
 
 
 ## Proxy Code Explained
@@ -197,22 +212,34 @@ It is composed of three endpoints as seen above. The first endpoint to be called
 
 #### auth
 
-Originally called from a cozy-stack trying to setup its enedis konnector. The proxy gets this informations from the query:
+Originally called from a cozy-stack trying to setup its konnector. The proxy gets these informations from the query:
 
-- clientId
+- client_id
+- duration
+- redirect_uri (auto inserted by the cozy-stack, except if you specify **skip_redirect_uri:true** in the couchdb)
+- response_type
 - state (as it was conceived by the cozy-stack)
-- redirect_uri (**will be used later to trace back the stack**)
 
-With all these informations, the proxy can contact enedis **/auth** endpoint to start the oauth dance.
+![auth_params](enedis-auth-params.png)
+
+The state will be merged with the instance name, then decomposed again when reaching /redirect. This way the proxy is able to keep track of the cozy instance originally calling.
+
+With all these informations, the proxy can contact the provider **/auth** endpoint to start the oauth dance.
+
+##### Enedis
 
 !!! warning "note"
     See that a new composed state is sent to enedis, it is made of the former state conceived by the cozy-stack + the cozyOrigin instance name. This will be usefull when enedis is leading the oauth dance to the next step and we will need the name of the cozy to answer.
 
 Once the call is sent, enedis will point to the **/redirect** endpoint.
 
+##### Grdf
+
+> To be redacted
+
 #### redirect
 
-Retrieve the *code*, *usage_point_id*, and*state* answered by Enedis.
+Retrieve the *code*, *usage_point_id*, and *state* answered by Enedis.
 
 Split the customed state that was modified in the **/auth** process. From this split it creates two variables :
 
@@ -221,11 +248,15 @@ Split the customed state that was modified in the **/auth** process. From this s
 
 Finally redirect all these parameters in a query to the cozy-stack (the cozy-stack which is still waiting for an answer from its /auth call).
 
+!!! warning "state / instance"
+    The state must be recovered without the instance name, otherwise the cozy-stack won't recognized it and the handshake will fail.
+
 #### token
 
 Gathering from query or parameters all params.
 
-Sends a post request to enedis /token endpoint. 
+Sends a post request to the provider /token endpoint. 
 The stack will store the response params in a *accounts* couchdb database.
 
-## What Happens Next
\ No newline at end of file
+## What Happens Next
+
diff --git a/docs/proxy/enedis-auth-params.png b/docs/proxy/enedis-auth-params.png
new file mode 100644
index 0000000000000000000000000000000000000000..829d96e5eb9e0daac815eec8b1d68acb39120c76
Binary files /dev/null and b/docs/proxy/enedis-auth-params.png differ
diff --git a/mkdocs.yml b/mkdocs.yml
index 8c761778d24756b373694b6263a216d4783acec1..d0c527122602e7ce44e83dbcf7b9233ca86970bb 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -15,8 +15,6 @@ theme:
 markdown_extensions:
   - admonition
   - attr_list
-  - plantuml_markdown:
-      server: http://www.plantuml.com/plantuml
   - pymdownx.emoji
 
 nav: