Device Authorization flows appears to lose tenantId

[stuartdoyle]

Hi,

We're making use of the Oauth Device Authorization flow and we're passing the tenantId to the /oauth2/authorize endpoint, together with the user loginId and password. We have our own tenant that we're using (so not the default tenantId).

Prior to 1.19 (specifically in 1.17), the final redirect to the device-complete page resulted in our own tenant's theme being applied. However, since 1.19, even though we're sending the tenantId, it seems to get lost in the redirects and reverts to the default theme.

I can see that the redirect from /oauth2/authorize to /oauth2/device does not include the tenantId and then the next redirect from /oauth2/device to /oauth2/device-complete includes the Default tenantId.

Is there new config or parameter that we've missed? Or is this a genuine bug that needs to be logged?

Thanks,

Stuart

[dan]

This seems like a bug. Please file it here: https://github.com/fusionauth/fusionauth-issues/issues