Thema "Betreff: Problems getting the access token" in Getting started programming with the Viessmann API

Problems getting the access token

JueBag — Sat, 19 Jun 2021 11:10:50 GMT

I am observing problems getting the access token as described in the developer portal.

Intitially I am trying to get the token manually by http requests in order to understand the procedure, the final goal is to implement the whole procedure into openHAB using rules and later maybe a complete binding (i.e. create a standard interface from openHAB to the Viessmann API useable for others as well).

My current problem/question:

I managed to get past Step 1 and received a code using the posted http request like:

https://iam.viessmann.com/idp/v2/authorize?client_id=my_oauth_client_id&redirect_uri=http://localhost:4200/&response_type=code&code_challenge=my_code_challenge&scope=IoT%20User

(my_oauth_client and my_code_challenge are replaced with my actual values).

Using the received code I posted:

https://iam.viessmann.com/idp/v2/token?client_id=my_oauth_client&redirect_uri=http://localhost:4200/&code_verifier=my_code_challenge&code=my_received_code

I used the same string for My_code_challenge in both cases (in my understanding without setting code_challenge_method this should be correct).

From such I always get:

{"error":"invalid-authorization-request"}

What am I doing wrong?

I tried to send the second request as fast as possible (at least within a minute). Am I to slow?
The developer portal showed only a cURL example for the second request, is my selfmade https string wrong?
....

As a follow up question, the to be received API token has a setting of

"expires_in": 3600

Is that seconds or minutes?

Betreff: Problems getting the access token

andreas13 — Sun, 20 Jun 2021 18:34:51 GMT

I am missing: "grant_type=authorization_code"

Betreff: Problems getting the access token

JueBag — Mon, 21 Jun 2021 05:40:04 GMT

Thanks for the input, however using:

https://iam.viessmann.com/idp/v2/token?grant_type=authorization_code&client_id=my_oauth_client&redirect_uri=http://localhost:4200/&code_verifier=my_code_challenge&code=my_received_code

I'm getting

{"error":"invalid-token-request"}

as well.

Betreff: Problems getting the access token

CustomerCareMichael — Mon, 21 Jun 2021 06:19:03 GMT

Hi @JueBag ,

within the second step (Authorization code exchange), have you set the parameter within the header?

-H "Content-Type: application/x-www-form-urlencoded"

Also, make sure to send a POST request.

The expiration time of the token is in seconds. However, you can create a refresh token, which helps you obtaining a new access token much easier, as you do not need to do step 1 (Authorization request) anymore. You find the explanation for the refresh token here: https://developer.viessmann.com/en/doc/authentication (Refreshing an access token)

Hope this helps. If you have further questions, let me know.

Best,

Michael

Betreff: Problems getting the access token

JueBag — Mon, 21 Jun 2021 07:38:29 GMT

@CustomerCareMichael

My trials to send a "POST" request solely with the browser didn't work, using POSTMAN I got my token.

Danke!

Follow-Up Question:

Will the Refresh-Token stay the same over time, or did I get the same on my second request just because it was within a short time?

Betreff: Problems getting the access token

CustomerCareBen — Mon, 21 Jun 2021 11:43:22 GMT

Der Beitrag wurde automatisch verschoben.

Betreff: Problems getting the access token

nigolcabej — Mon, 18 Oct 2021 14:55:20 GMT

Hi,

the above link doesnt work.

I have a problem with this line:

curl -X POST "https://iam.viessmann.com/idp/v2/token" -H "Content-Type: application/x-www-form-urlencoded" -d "grant_type=authorization_code&client_id=xxxxxxxxxxxxxxxxxxx&redirect_uri=http://192.168.1.199:8123&code_verifier=yyyyyyyyyyyyyyyyyyyyyyyy&code=zzzzzzzzzzzzzzzzzzz"

the code i've got already. It was not easy because the redirect_uri redirects immediatellay to an other site and i had to be very fast with the screeenshot :)...finally i've got it, but I get with the above curl a response:

{"error":"invalid-token-request"}

why? what is wrong?

and why it is so complicated: request via url, curl, tokens, client_id, code_verifier, codes, logins? It is an access for my-all-live-savings in a super secure bank? why the client_id is not enough?

regards

Andrzej

Betreff: Problems getting the access token

JueBag — Mon, 18 Oct 2021 17:35:03 GMT

@nigolcabej schrieb:

It was not easy because the redirect_uri redirects immediatellay to an other site

You did set that url! Why didn't you use localhost?

Betreff: Problems getting the access token

nigolcabej — Mon, 18 Oct 2021 19:56:58 GMT

Hi,

to get the "code" and it have been worked with this url. so it doesnt matter, i suppose, what is the redirect_uri. Why i'm getting the {"error":"invalid-token-request"}?

Regards

Betreff: Problems getting the access token

MrAnderson — Tue, 02 Nov 2021 10:23:12 GMT

Hi,

I'm a bit puzzled... I also get "invalid-token-request" when trying this on the command line.

Here is my script:

#!/bin/bash

export client_id="client_id"
export redirect_uri="http://localhost:4200/oauth-callback"
export challenge_id=$(cat /proc/sys/kernel/random/uuid)
export email="email"
export password="password"

# Authorize and get code for further request
curl -X POST "https://iam.viessmann.com/idp/v2/authorize?client_id=$client_id&redirect_uri=$redirect_uri&response_type=code&code_challenge=$challenge_id&scope=IoT%20User" \
-d "hidden-password=00&stayloggedin=Angemeldet bleiben&submit=Login&isiwebuserid=$email&isiwebpasswd=$password" \
-o login.html
export code=$(grep $redirect_uri login.html | sed -E 's/(^.*code=)([^"]*)(.*)/\2/g')

# get access token
curl -H "Content-Type: application/x-www-form-urlencoded" \
-X POST "https://iam.viessmann.com/idp/v2/token" \
-d "grant_type=authorization_code&code_verifier=$challenge_id&client_id=$client_id&redirect_uri=$redirect_uri&code=$code" \
-o access_token.json

Am I missing somehting and cannot see it?