jakepronger

Fixes issue #4

I've noticed this myself and don't think it evens works now even with a device already registered. Will look into this later when I get more time, but it does...

> Yes enrolling fails for me after the OTP step too. But using my existing credentials still works. > > I will look into the passkey route as that should...

I need to understand the structure of the request referencing this section of code ```py # Authenticate with long life token. response = client.post( "https://api.ubank.com.au/app/v1/long-life-token/login", json={ #"authKey": device.auth_key, "deviceUuid": device.device_id,...

I can use inspect element and connect my mobile to track all of the requests and see it's contents. I've done some things but the authKey is missing from one...

Is it the same value as 'token' or should be different?

They don't send an authKey in the otp response anymore. Nothing new in the headers either. This is all we are given in the otp response: ```json { "accessToken": "",...

Not sure what can be done about this but still looking into it. I'm not able to replicate any long life token requests using the app normally in any way...

Very interesting. If only there was a way to find that auth key that they are not providing us. My old auth key doesn't work but I'm pretty sure that's...

The flowId is an easy fix just by providing it in the otp_response post. ```py # Authenticate with second factor: a security code sent to mobile. otp_response = client.post( url="https://api.ubank.com.au/app/v1/challenge/otp",...