Passport Auth Strategy

thefrontend

6 months ago

11

import { CollectionConfig } from 'payload/types';
import { isLoggedIn } from '../access/isLoggedIn';
import { verifyEmail } from '../emails/verifyEmail';
import { forgotPassword } from '../emails/forgotPassword';
import AppleStrategy from '../auth/apple';

// import passport from "passport";
const Users: CollectionConfig = {
  slug: 'users',
  auth: {
    cookies: {
      sameSite: 'none',
      secure: true,
    },
    strategies: [
      {
        name: 'apple',
        strategy: AppleStrategy
      },
    ],
    verify: {
      generateEmailHTML: verifyEmail,
    },
    forgotPassword: {
      generateEmailHTML: forgotPassword,
    }
  },
  admin: {
    useAsTitle: 'email',
  },
  access: {
    create: () => true,
    read: isLoggedIn,
  },
  fields: [
    
  ],
}

export default Users;

import Strategy from "passport-apple";

const AppleStrategy = new Strategy(
  {
    clientID: "XXX",
    teamID: "XXX",
    callbackURL: "XXX",
    keyID: "XXX",
    privateKeyLocation: "XXX",
    passReqToCallback: true
  },
  function(req, accessToken, refreshToken, idToken, profile, cb) {
    // 
    cb(null, idToken);
}

);

export default AppleStrategy;

• 

  notchr

  6 months ago

  @thefrontend What's the apple auth code look like?

• 

  thefrontend

  6 months ago

  I just updated the original post above, there is not much going on. I just copied and configured the blank code from passport js.

  
  
  

  Also my payload config looks like this

  
  
  

  payload.config.ts

  
  

  import { buildConfig } from 'payload/config';
  import path from 'path';
  
  import AdminUsers from './collections/AdminUsers';
  import Users from './collections/Users';
  
  const createStripeSubscriptionPath = path.resolve(__dirname, 'auth/apple');
  const mockModulePath = path.resolve(__dirname, 'mocks/emptyObject');
  
  export default buildConfig({
    serverURL: process.env.APP_URL,
    csrf: [
      'https://localhost:5173',
    ],
    admin: {
      user: AdminUsers.slug,
      meta: {
        titleSuffix: '- Demo',
      },
      webpack: (config) => ({
              ...config,
              resolve: {
                  ...config.resolve,
                  alias: {
                      ...config.resolve.alias,
                      [createStripeSubscriptionPath]: mockModulePath,
                  }
              }
          })
    },
    collections: [
      AdminUsers,
      Users,
    ],
    typescript: {
      outputFile: path.resolve(__dirname, 'payload-types.ts'),
    },
    graphQL: {
      disablePlaygroundInProduction: false,
      schemaOutputFile: path.resolve(__dirname, 'generated-schema.graphql'),
    },
  });

• 

  notchr

  6 months ago

  Weird, looks OK to me

  
  

  
  

  and it's redirecting on the login page?

  
  

  
  

  how so

• 

  thefrontend

  6 months ago

  Now I only run into CORS issues on the login page but it's still redirecting when trying to open /api/graphql-playground

  

  
• 

  notchr

  6 months ago

  Hmm that's showing your request is failing though

  
  

  
  

  Is your allowed origins set on apple dev side?

• 

  thefrontend

  6 months ago

  There is nothing I can really set manually. I did enter the domains that are allowed to use sign-in-with-apple

  
  

  
  

  the exact same happens when I use the passport-google-oauth20 library. Must be missing something here 🤨

  
  

  
  

  @jmikrut any ideas on this? I also noticed once I add multiple strategies it always tries to redirect me to the one at the end of the array. When I try to open the graphql-playground or any api route it always redirects me to the external auth page (google in this case)

• 

  jmikrut

  Payload Team

  6 months ago

  So this is a problem with many Passport SSO plugins

  
  

  
  

  they are built to redirect

  all

  routes that they "protect" to the SSO auth page (in this case, apple). Even API routes. So when you load the dashboard, and the dashboard makes requests to /api/users/init, and /api/users/me, etc etc - -

  those

  requests are actually also incorrectly being redirected to your SSO login page... and showing CORS errors that result from Apple / Google / wherever

  
  

  
  

  that's the tough part with SSO. 99% of the existing plugins out there are meant to redirect

  all

  routes if you are not authenticated, when really, you only want to redirect anything on /admin, and leave the /api routes alone. API routes should remain left as-is, because it should be possible to hit those routes without being authenticated

  
  

  
  

  there are different "strategy" methods out there - some are "bearer strategies" - and this is what you want. Basically, leave it up to the user to either auth or not auth, via header or cookie or similar. If no cookie / header / etc is found, they are simply not authenticated and the route proceeds as normal.

  
  

  
  

  but TL;DR, your CORS error is a red herring and is not the real issue here. What's really happening is that those requests are incorrectly being redirected

• 

  supaku

  2 weeks ago

  @thefrontend Did you end up finding a path forward here? I've also set up

  passport-google-oauth20

  as well and have arrived where you did. I previously got the payload oauth plugin(

  https://github.com/thgh/payload-plugin-oauth/blob/main/src/index.ts

  ) to work, but wanted to be able to add multiple strategies and found myself on this path.

• 

  Rick | Byont Labs

  3 days ago

  yeah, same thing here

• 

  wizen3380

  3 days ago

  Do you guys have any working example on how to authenticate via google oauth on payload?

• 

  Rick | Byont Labs

  2 days ago

  This thread gave me some additional insights in other ways to implement authentication, haven't gotten to google auth yet but I can login with my own endpoint by getting the user from the database, creating a jwt token and setting it in the payload cookie.

  
  https://discord.com/channels/967097582721572934/1073356002101035108
  
  

  The thread says to disable localAuthStrategy though, which I haven't needed to do. I wonder why that is..

  
  

  Perhaps im still to run into that limitation as I work on integrating googleAuth in this endpoint