Hi all. I’ve added a reply here about why we won’t be taking this forward (for now).
In short, we don’t want to enable an undesirable precendent by exposing the ID token directly from the SDK, until we have a good enough case to do so. Because Hasura don’t specifically require an ID token, we don’t feel that the Hasura case is a strong enough reason to enable this feature in the SDK at the moment. We would however be very interested in other examples where this would be needed.
@tehpsalmist if you need some help migrating from an ID token to an access token for this scenario, please let us know! Hasura also have a webhook authentication mode if that is another option for you, but I have a feeling that using the access token will be easier.