You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of the Keycloak APIs I need for the GraphQL API require a KeycloakSession. Luckily, the Keycloak REST infrastructure creates one (a QuarkusKeycloakSession) in the REST provider on each REST handler invocation. For subscriptions, the query is re-executed every time the subscription fires and the resolvers need to be passed a KeycloakSession. So the question is: how do we create a valid KeycloakSession on the server side whenever the subscription event is fired? This session should represent the User/Principal that made the original request to create the subscription
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Most of the Keycloak APIs I need for the GraphQL API require a KeycloakSession. Luckily, the Keycloak REST infrastructure creates one (a QuarkusKeycloakSession) in the REST provider on each REST handler invocation. For subscriptions, the query is re-executed every time the subscription fires and the resolvers need to be passed a KeycloakSession. So the question is: how do we create a valid KeycloakSession on the server side whenever the subscription event is fired? This session should represent the User/Principal that made the original request to create the subscription
Beta Was this translation helpful? Give feedback.
All reactions