Login

[elueckel]

Hi,
I am trying to build a similar class using PHP to be integrated into my home automation.

What I am struggling with is how the login mechanics work. In stage 1 the login class with authenticate - that works well for me and I get a cookie. What I am not able to do is to reuse the login to call any other function e.g. self ...

Can you give me a hint how the authentication works beyond the base method ...?

Thanks

Enno

[malle-pietje]

First of all, why would you wish to recreate this class? Second; this class stores the extracted cookie in a private property for reuse later.

[elueckel]

Thanks - I got it working. The reason for the recreation would be, that your call is to powerful and I only need a small subset of functions. As such the current version has too many options to swiftly maintain it in the cloud Text I intend using it. However - your work is really a great foundation.

…

Am 08.08.2021 um 12:00 schrieb malle-pietje ***@***.***>:  First of all, why would you wish to recreate this class? Second; this class stores the extracted cookie in a private property for reuse later. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[thib3113]

just to be sure, because the authentification mechanism doen't work in the same way with unifiOS or not . Did you manage the two ? ( or else you support only one ? )

( I got the same problem in node.js ;) )

[malle-pietje]

Good to hear, and you’re welcome!

[elueckel]

Yeah - saw that. Thanks for the hint. My biggest issue for now was getting the cookie transferred, but finally I solved that.

…

Am 08.08.2021 um 13:11 schrieb Thibaut SEVERAC ***@***.***>:  just to be sure, because the authentification mechanism doen't work in the same way with unifiOS or not . Did you manage the two ? ( or else you support only one ? ) ( I got the same problem in node.js ;) ) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[thib3113]

@jenkins316 maybe need to add the CSRF token in the headers ?

[malle-pietje]

Have a look here:
https://github.com/Art-of-WiFi/UniFi-API-client/blob/master/src/Client.php#L3731-L3751

[elueckel]

here is my code derived from this project. it is a bit shorter and maybe a bit easier to read

https://github.com/elueckel/Unifi-Toolbox/blob/main/UniFi%20Presence%20Manager/module.php

[jenkins316]

It matches the header used during the /api/self/sites GET request which does work. Here is the raw request being logged:

POST /api/s/default/cmd/sitemgr HTTP/1.1
User-Agent: OpenEdge-HttpClient/0.4.0 (WIN32/32) OpenEdge/11.7.6.0.2049 Lib-ABLSockets/0.5.0
Host: xxxxxxxx.net:8443
Cookie: unifises=OS8xVyQc--------7AFYUr1X4fb; csrf_token=11Q0lxL------------MD9mzAdGW7d
Content-Type: application/json
Content-Length: 40
Accept: application/json

{"desc":"00-Hi John-2","cmd":"add-site"}

This seems so straight forward. No idea why I keep getting 401 LoginRequired. Does a POST require the token to be named 'x-csrf-token' or some additional decoding of the token? I found this in one of the Readme files, is this what I am missing?:

Added GetAllCookies to the HttpUtility which allows extracting the cookies from the cookie container. This is required as UniFi demands the cross site request forgery token stored in the cookie to be passed through the custom X-Csrf-Token header on every HTTP Post.

[jenkins316]

That was exactly what it was. Even though the cookies are in the POST, still had to add that same cookie value with a name of 'X-Csrf-Token' to the header. Strange that it works without it in a curl command. Thanks all for pointing me in the right direction.