authentication: Update calls to use the new client id/secret

source/guidelines/authentication.rst

@@ -105,22 +105,27 @@ is the method shown here.
 
 .. rubric:: Request an access token
 
-In order to receive an access token, you need in advance to have
-credentials for the Open Data Hub. If you do not have them, please
-open a ticket on issues.opendatahub.bz.it or send an email to
-:email:`help@opendatahub.bz.it`.
-
-With your username and password
-(:strong:`my_username`. :strong:`my_password`), the access token is
-granted to you with the following call:
+In order to receive an access token, you need in advance to have credentials for
+the Open Data Hub. If you do not have them, please open a ticket on
+issues.opendatahub.bz.it or send an email to :email:`help@opendatahub.bz.it`.
+The same holds, if you plan to create an application that retrieves closed data
+from the Open Data Hub. For this, also other OAuth2 flows exist.
+
+With your username and password, and a client secret (:strong:`my_username`,
+:strong:`my_password`, :strong:`the_client_secret`), the access token is granted
+to you with the following call:
 
 .. code-block:: bash
    :name: grant-token
    :caption: Receiving an access topic
 
-   curl -X POST -L -H 'Content-Type:application/x-www-form-urlencoded' \
-   "https://auth.opendatahub.bz.it/auth/realms/noi/protocol/openid-connect/token" \
-   -d 'grant_type=password&username=my_username&password=my_password&client_id=odh-mobility-v2'
+   curl -X POST -L "https://auth.opendatahub.bz.it/auth/realms/noi/protocol/openid-connect/token" \
+   --header 'Content-Type: application/x-www-form-urlencoded' \
+   --data-urlencode 'grant_type=password' \
+   --data-urlencode 'username=my_username' \
+   --data-urlencode 'password=my_password' \
+   --data-urlencode 'client_id=odh-generic-client' \
+   --data-urlencode 'client_secret=the_client_secret'
 
 Since the token expires after a given amount of time, it might prove
 necessary to refresh it, an action that can be done by replacing the
@@ -130,9 +135,12 @@ parameters given in the query above with
    :name: refresh-token
    :caption: Refreshing the access token
 	  
-   curl -X POST -L -H 'Content-Type:application/x-www-form-urlencoded' \
-   "https://auth.opendatahub.bz.it/auth/realms/noi/protocol/openid-connect/token" \
-   -d 'grant_type=refresh_token&refresh_token=*****&client_id=odh-mobility-v2'
+   curl -X POST -L "https://auth.opendatahub.bz.it/auth/realms/noi/protocol/openid-connect/token" \
+   --header 'Content-Type: application/x-www-form-urlencoded' \
+   --data-urlencode 'grant_type=refresh_token' \
+   --data-urlencode 'refresh_token=the_refresh_token' \
+   --data-urlencode 'client_id=odh-generic-client' \
+   --data-urlencode 'client_secret=the_client_secret'
 
 Here, use the refresh token received from :numref:`grant-token`.
 
@@ -147,10 +155,9 @@ requests. The following API call shows how to get all
    :name: get-closed-data
    :caption: Retrieving data with the access token
 
-   curl -X GET \
-   'https://mobility.api.opendatahub.bz.it/v2/api/flat/VMS/*/latest?select=sname,mvalue' \
-   -H 'content-type: application/json' \
-   -H 'Authorization: bearer your-access-token'
+   curl -X GET "https://mobility.api.opendatahub.bz.it/v2/flat/VMS/*/latest?select=sname,mvalue" \
+   --header 'Content-Type: application/json' \
+   --header 'Authorization: bearer your-access-token'
 
 Currently, data retrieved from the Open Data Hub are always open,
 except for some of the latest values and historical data: Only a