Where on VRM Portal can we manage 'personal access tokens' for usage with external services?
asked
VRM Portal and Personal Access Tokens
Hi @bww,
VRM access token management (to the extent that it is offered) is described in the VRM API documentation - https://vrm-api-docs.victronenergy.com/#/
So have I to write a program where user give me login, password to generate personal token? This is not more secure than just login by login and password.
Can I use personal token to login to mqtt?
Hi @bww
The access token model is required when enabling 2FA for additional security.
So then you can have a unique token for each service, and not disclose your main password.
We are testing a VRM update to give more user control over access tokens, including the ability to add new ones from the UI, & revoke access to old ones.
I'll post an update here when it is released.
You can now control your access tokens in VRM. To do that, go to preferences -> integrations -> access tokens in VRM!
Hi - I can't find any preferences in VRM portal. Has this been moved somewhere? I am a full rights user on my account. Also if I try creating access tokens via the API and using a bearer token from login I get "You do not have sufficient rights... " error message. Any help appreciated as I am unable to use the API at present.
Thx.
Exceptionally good news. I'm waiting. When users can be able to generate token than I will immediately add tokens to GbbVictronWeb.gbbsoft.pl program.
But what about mqtt access using token?
I generate token for myself (using beta version of VRM)
I put it to my program gbbvictronweb.gbbsoft.pl
Program put it to 'X-Authorization' as: Token <token>
And receive following error: Invalid access token received
I wanted to call: https://vrmapi.victronenergy.com/v2/installations/xxxxxx/stats?type=live_feed&interval=hours&start=1687125600&end=1687211999
Did you replace the xxxxxx after the /installations with the actual site ID?
Now open issue is using token to login to MQTT on mqtt{index}.victronenergy.com
For anyone having trouble with the authentication in VRM to authorize VictronConnect, The AppImage, at least as of 5.91 version of VictronConnect, has a need to have OpenSSL version 1.1 installed. New distributions use OpenSSL version 3, which has remove some of the functions. Under Fedora 38, this is easily fixed by `sudo dnf install openssl1.1`. Restart VictronConnect, and you should be in better shape. Hopefully the team with @mvader (Victron Energy) is able to make note of this or update the AppImage to work directly with newer Linux distributions.
The work done to bring VictronConnect to us Linux types is greatly appreciated.
