Custom auth - problem with getcurrentUser and protected routes

peterp · August 7, 2020, 7:43am

I think the problem is here:

You’re passing the raw “authClient” to redwood without mapping the values. You’ll need to map the “shape” of Msal to match that which Redwood expects, what I mean by this is that Redwood expects your client object to have the following named functions that return the correct values:

github.com

redwoodjs/redwood/blob/3614b6d4cf577f7840d0ba2fc80975a258326c5f/packages/auth/src/authClients/index.ts#L40-L49


      
          export interface AuthClient {
            restoreAuthState?(): void | Promise<any>
            login(options?: any): Promise<any>
            logout(options?: any): void | Promise<void>
            getToken(): Promise<null | string>
            /** The user's data from the AuthProvider */
            getUserMetadata(): Promise<null | SupportedUserMetadata>
            client: SupportedAuthClients
            type: SupportedAuthTypes
          }

You can see the implementation of various other clients over here: https://github.com/redwoodjs/redwood/tree/main/packages/auth/src/authClients

As an example; if new Msal returns an object that has a LogInWithPopUp method, you would have to map this method like this:

const originalAuthClient = new Msal.UserAgentApplication(msalConfig)

const myAuthClient = {
    type: 'custom',
    client: originalAuthClient,
    login: originalAuthClient.LogInWithPopUp,
   /* ...  implement getToken, logout, getUserMetadata */
}