Undefined access token

After calling const keycloak = new Keycloak( { … } ) with my configurations (i believe secret should be inside credentials - credentials: {secret: …} )

In my case my ApolloServer is like this

const apolloServer = new ApolloServer({ async context({ connection, req }) { const context = { …contextFromOptions };

    // For a GraphQL subscription WebSocket request, there is no `req`
    if (connection) return context;

  await createDataLoaders(context);
  
  context.kauth = new KeycloakContext({ req });

  console.log(context.kauth.accessToken);
  
  return context;
},
debug: options.debug || false,
formatError: getErrorFormatter(),
schema,
subscriptions,
introspection: config.GRAPHQL_INTROSPECTION_ENABLED,
playground: config.GRAPHQL_PLAYGROUND_ENABLED

});

I put a ocnsole log to view accessToken in context but it’s returning undefined. how can i debug and know that request is being made and view the keycloak response?

[wtrocki]

The access token will not be available in the context method - it will be available in resolvers like demoed in the example applications. The context method is used to create object and it is not used to authenticate or have info about user.

It might happen that request is missing access token. This usually happens when we forget to add keycloak middleware/protect graphql route.

Also it is worth to include version of the keycloak adapter that is being used. Some issues with old adapters might happen (we also did not tested version 11 of the adapter)

[wtrocki]

what do you mean “use a public client from keycloak”?

Keycloak have two client types. Bearer and Public. Bearer client is used only for backends to check token - it doesn’t provide login logic/session etc.

are you saying that context.kauth.accessToken should not contain the Bearer access token?

That would be part of the keycloak node.js library logic. All we do here is export this logic to graphql layer.