Is it possible to implement the hydra consent workflow without a cache?
At the end of the callback function we’d like to return the JSONAPI data related to the user that has consented. However, the request to handleCallback doesn’t appear to have any data related to the user, only to the token information. We tried adding the profile ID to the redirect URI as a query param; however hydra strips it out by the time we hit the callback.
This suggests we either have to cache the user/token from an earlier request (login or consent) or we’re missing something about how to pass user-information to the redirect URI which the callback API handles.
Unlike the example app, we don’t have this all in one file. We would prefer our consent app to remain stateless.
Is there a way to pass information between the login & consent that would be visible by the time the callback request is made - even if its just a user id? Or is there something we’re misunderstanding?
Thanks for your help in advance.