Infinite loop in geAuth

[koush]

Is there an existing issue for this?

• I have searched the existing issues

Describe The Bug

https://github.com/dgreif/ring/blob/main/packages/ring-client-api/rest-client.ts#L268

Doesn't this line cause a recursive request loop on a service or connection failure?

To Reproduce

No response

Expected behavior

N/A

Relevant log output

No response

Screenshots

No response

Additional context

No response

OS

All

Node.js Version

All

NPM Version

N/A

ring-client-api

11

Operating System

All

[koush]

Nevermind, I was having a hard time following the code. authConfig gets cleared. It does seem like there's an issue here where any service/connection failure clears the auth.

[tsightler]

I think this is a duplicate of my issue here: #1071

[koush]

@tsightler yeah, I am not sure why the refresh token is ever cleared. If the client enters a auth failure state, the failures should continue with the last known refresh token, which may recover. But as of now it clears the refresh token and guarantees it will never recover.

[tsightler]

I think it's just because the same code path is used for the initial authentication so, for example, if there is a configured token, but that saved token isn't valid, it's cleared so the same code path can be used to re-authenticate via standard 2FA auth. That's actually fine for the case where the token truly is invalid (for example, user removes account from authorized devices), but it's not good for the case where the token is only temporarily not working, which is the far more common case, in my experience.

[koush]

Yeah, gonna try this and see if it works better. I don't think the rest client should be responsible for refresh token clearing. That requires user interaction, and it happens silently now. koush@4e95093