Auth Strategies

[pedroslopez]

Cleans up the new local file storage and legacy auth into separate Auth Strategies.

This concept could be used later to add something like S3Auth, for example. It also means users can develop their own auth strategies.

Usage

LocalAuth - Filesystem-based auth that uses puppeteer's userDataDir to persist browser data

const client = new Client({
    authStrategy: new LocalAuth()
});

To customize clientId or dataPath, pass as options to the auth strategy:

const client = new Client({
    authStrategy: new LocalAuth({
        clientId: "example",
        dataPath: "./some/path"
    })
});

LegacySessionAuth - traditional method that pulls tokens from local storage

Not available for MD.
Used by default if a session option is passed to the client, but this is only for backwards compatibility.

const client = new Client({
    session: { } // session data here from wherever you get it from
});

Should be used explicitly to be able to get the payload in the auth event without passing a session:

const client = new Client({
    authStrategy: new LegacySessionAuth({
        session: { } // session data here from wherever you get it from
    })
});

NoAuth - does not provide any auth saving

Used by default if no session option is passed

const client = new Client({
    authStrategy: new NoAuth()
});