Doesn't work when 2FA is active

[dartiss]

When I try and use the Open Homebridge UI option and specify my credentials, I get this error...

Unsuccessful login: Server is unavailable or login/password is incorrect. {"statusCode":412,"message":"2FA Code Required"}

My assumption here is that this is because I have 2FA on my account. Is there a way around this?

[sergey-tihon]

@dartiss what 2nd factor do you use?
Can you please briefly describe our auth flow?

[dartiss]

Hi,

I'm using the built-in 2FA which makes use of app authentication.

Within the Stream Deck app, I'm providing the server address, user name and password, as per my Homebridge account. That's when I get the above error.

[ethanlevine]

I receive the same response when trying to log in, also when using 2FA via app authentication in Homebridge.

[sergey-tihon]

Can you point to the manual on how you configured 2FA in Homebridge?

[johnnygoodface]

In Homebridge, you go into User Accounts, then click on Enable 2FA. Then you scan the QRCode in your preferred Authenticator app. This being said, your plugin works ok when 2FA is off.
The only issue I get, is that when I change a switch state into Home or homebridge, it's not reflected in Stream Deck

[ryan7g49i27653]

I have the same issue. Within home bridge, under Settings -> User Accounts, I have my admin user with 2FA enabled. Essentially, a successful username and password challenge is followed-up with a challenge for my token code. Once that token code is entered and accepted, I am then past the authentication challenge. So essentially, for this plugin to work when Homebridge has 2FA enabled, it would need to read the response, understand that there is 2FA enabled, and then accept and pass the token credential back to Homebridge.

[sergey-tihon]

I don't fully understand how to support it ...

The plugin actually has 2 parts

1. Property Inspector - the UI where you configure actions. Here 2FA is not an issue, because we have UI and you can type a token during action configuration.
2. Plugin itself that remain running when you close streamdeck app.

Current implementation store login & password inside streamdeck and re-auth when needed without your participation (Default session lifetime is 8h). With 2FA plugin cannot authenticate without user and don't have UI.

• You definitely will not like open streamdeck and re-auth every 8h.
• i believe you can increase livetime of the token to days instead of hours, but in this case we lose benefits of 2FA...