Launch Apollo Studio


Unless all of the data you are loading is completely public, your app has some sort of users, accounts and permissions systems. If different users have different permissions in your application, then you need a way to tell the server which user is associated with each request.

Apollo Client uses the ultra flexible Apollo Link that includes several options for authentication.

If your app is browser based and you are using cookies for login and session management with a backend, tell your network interface to send the cookie along with every request. Pass the credentials option e.g. credentials: 'same-origin' if your backend server is the same domain, as shown below, or else credentials: 'include' if your backend is a different domain.

const link = createHttpLink({
  uri: '/graphql',
  credentials: 'same-origin'

const client = new ApolloClient({
  cache: new InMemoryCache(),

This option is passed through to the fetch implementation used by the HttpLink when sending the query.

Note: the backend must also allow credentials from the requested origin. e.g. if using the popular 'cors' package from npm in node.js, the following settings would work in tandem with the above apollo client settings:

// enable cors
var corsOptions = {
  origin: '<insert uri of front-end domain>',
  credentials: true // <-- REQUIRED backend setting

Another common way to identify yourself when using HTTP is to send along an authorization header. Add an authorization header to every HTTP request by chaining together Apollo Links. In this example, we'll pull the login token from localStorage every time a request is sent:

import { ApolloClient, createHttpLink, InMemoryCache } from '@apollo/client';
import { setContext } from '@apollo/client/link/context';

const httpLink = createHttpLink({
  uri: '/graphql',

const authLink = setContext((_, { headers }) => {
  // get the authentication token from local storage if it exists
  const token = localStorage.getItem('token');
  // return the headers to the context so httpLink can read them
  return {
    headers: {
      authorization: token ? `Bearer ${token}` : "",

const client = new ApolloClient({
  link: authLink.concat(httpLink),
  cache: new InMemoryCache()

The server can use that header to authenticate the user and attach it to the GraphQL execution context, so resolvers can modify their behavior based on a user's role and permissions.

Reset store on logout

Since Apollo caches all of your query results, it's important to get rid of them when the login state changes.

The most straightforward way to ensure that the UI and store state reflects the current user's permissions is to call client.resetStore() after your login or logout process has completed. This will cause the store to be cleared and all active queries to be refetched. If you just want the store to be cleared and don't want to refetch active queries, use client.clearStore() instead. Another option is to reload the page, which will have a similar effect.

const PROFILE_QUERY = gql`
  query CurrentUserForLayout {
    currentUser {

function Profile() {
  const { client, loading, data: { currentUser } } = useQuery(
    { fetchPolicy: "network-only" }

  if (loading) {
    return <p className="navbar-text navbar-right">Loading...</p>;

  if (currentUser) {
    return (
        <p className="navbar-text navbar-right">
            onClick={() => {
              // call your auth logout code then reset store
              App.logout().then(() => client.resetStore());
            Log out

  return (
    <p className="navbar-text navbar-right">
      <a href="/login/github">Log in with GitHub</a>
Edit on GitHub