@nestjs-hybrid-auth/linkedin/README.md

NestJS linkedin authentication using passport

# NestJS Linkedin Authentication

Implement linkedin authentication in your NestJS application.

## Install

```bash
npm install @nestjs-hybrid-auth/linkedin --save
```

OR

```bash
yarn add @nestjs-hybrid-auth/linkedin
```

## How To Use?

The package exports mainly a [dynamic module](https://docs.nestjs.com/fundamentals/dynamic-modules) and [guard](https://docs.nestjs.com/guards). The module should be imported in your app.module.ts and guards should be used on the route handlers of any controller.

## Example Code For app.module.ts

### Simple static configuration

Want to jump directly to the [available options](#linkedinauthmoduleoptions)?

If you just want to provide the static values or have them handy, pass them as options to the `forRoot` static method like below. The options object is type of `LinkedinAuthModuleOptions`.

```typescript
import { LinkedinAuthModule } from '@nestjs-hybrid-auth/linkedin';

@Module({
  imports: [
    LinkedinAuthModule.forRoot({
      clientID: process.env.CLIENT_ID,
      clientSecret: process.env.CLIENT_SECRET,
      callbackURL: process.env.CALLBACK_URL,
    }),
  ],
  controllers: [AppController],
  providers: [AppService],
})
export class AppModule {}
```

### `useFactory` to get the ConfigService injected.

If you want to make use of nest's [ConfigModule](https://docs.nestjs.com/techniques/configuration#installation) to get the auth configuration for a provider from `.env` config files, use `forRootAsync` static method. The options to this method are typeof `LinkedinAuthModuleAsyncOptions` which accepts a `useFactory` property. `useFactory` is a function which gets the instances injected whatever has been provided in `inject` array. You can use those instances to prepare and return the actual `LinkedinAuthModuleOptions` object. ConfigService can be one of them as per your choice.

```typescript
import { LinkedinAuthModule } from '@nestjs-hybrid-auth/linkedin';

@Module({
  imports: [
    ConfigModule.forRoot({
      isGlobal: true,
      cache: true,
      expandVariables: true,
    }),
    LinkedinAuthModule.forRootAsync({
      imports: [ConfigModule],
      inject: [ConfigService],
      useFactory: (configService: ConfigService) => ({
        clientID: configService.get('LINKEDIN_CLIENT_ID'),
        clientSecret: configService.get('LINKEDIN_CLIENT_SECRET'),
        callbackURL: configService.get('LINKEDIN_CALLBACK_URL'),
      }),
    }),
  ],
  controllers: [AppController],
  providers: [AppService],
})
export class AppModule {}
```

### Use `useClass` to get your auth config from a class

If the `useFactory` makes your app module bloated with a lot of boilerplate code, you can `useClass` to provide an existing config provider class. The class must implement `LinkedinAuthModuleOptionsFactory` interface and `createModuleOptions` method. This method should return `LinkedinAuthModuleOptions` object. Similar to `useFactory`, whatever you provide in `inject` array, it will get injected in the constructor of your class. Follow the example:

**hybrid-auth.config.ts**

```typescript
import { ConfigService } from '@nestjs/config';
import {
  LinkedinAuthModuleOptions,
  LinkedinAuthModuleOptionsFactory,
} from '@nestjs-hybrid-auth/linkedin';

@Injectable()
class HybridAuthConfig implements LinkedinAuthModuleOptionsFactory {
  constructor(private configService: ConfigService) {}

  createModuleOptions(): LinkedinAuthModuleOptions {
    return {
      clientKey: this.configService.get('LINKEDIN_CLIENT_ID'),
      clientSecret: this.configService.get('LINKEDIN_CLIENT_SECRET'),
      callbackURL: this.configService.get('LINKEDIN_CALLBACK_URL'),
    };
  }
}
```

**app.module.ts**

```typescript
import { LinkedinAuthModule } from '@nestjs-hybrid-auth/linkedin';

@Module({
  imports: [
    ConfigModule.forRoot({
      isGlobal: true,
      cache: true,
      expandVariables: true,
    }),
    LinkedinAuthModule.forRootAsync({
      imports: [ConfigModule],
      inject: [ConfigService],
      useClass: HybridAuthConfig,
    }),
  ],
  controllers: [AppController],
  providers: [AppService],
})
export class AppModule {}
```

## Example Code For Controller

Once you have setup the module properly in module file, its time to configure your route handlers to make the user properly redirected to appropriate identity provider's login page. `@nestjs-hybrid-auth/linkedin` provides a guard and result interface to make it enabled.

Each route will have two variants. One is to redirect to social login page and the other is to collect the response such as access/refresh tokens and user profile etc. The result will be attached to `Request` object's `hybridAuthResult` property as shown in the example below.

### app.controller.ts

```typescript
import {
  UseLinkedinAuth,
  LinkedinAuthResult,
} from '@nestjs-hybrid-auth/linkedin';

@Controller()
export class AppController {
  constructor(private readonly appService: AppService) {}

  @UseLinkedinAuth()
  @Get('auth/linkedin')
  loginWithLinkedin() {
    return 'Login with Linkedin';
  }

  @UseLinkedinAuth()
  @Get('auth/linkedin-login/callback')
  linkedinCallback(@Request() req): Partial<LinkedinAuthResult> {
    const result: LinkedinAuthResult = req.hybridAuthResult;
    return {
      accessToken: result.accessToken,
      refreshToken: result.refreshToken,
      profile: result.profile,
    };
  }
}
```

## Exports

`@nestjs-hybrid-auth/linkedin` exports various decorators, interfaces and methods.

### UseLinkedinAuth

`UseLinkedinAuth` is NestJS `Guard` which hijacks your nest request and redirects users to the appropriate login page of your configured identity provider (linkedin in this case). The same guard can be used on `callback` route also as shown in the example above. In the callback route handler, the `req: Request` object will have a property `hybridAuthResult` which is an object of type `LinkedinAuthResult`.

```typescript
@UseLinkedinAuth(options: LinkedinAuthGuardOptions)
@Get('auth/linkedin')
loginWithLinkedin() {
  return 'Login with Linkedin';
}
```

### LinkedinAuthGuardOptions

This is a simple object to be passed into `UseLinkedinAuth` guard as shown in example above if you want to pass some extra parameters to query the linkedin result. It can be left empty for default result.

### LinkedinAuthModule

This is the dynamic module which must be imported in your app's main module with `forRoot` or `forRootAsync` static methods whichever suits your need. Both will return a [NestJS dynamic module](https://docs.nestjs.com/fundamentals/dynamic-modules).

```typescript
interface LinkedinAuthModule {
  forRoot(options: LinkedinAuthModuleOptions): DynamicModule;
  forRootAsync(options: LinkedinAuthModuleAsyncOptions): DynamicModule;
}
```

### LinkedinAuthModuleOptions

If you are configuring your module with `forRoot` static method, pass in the module options given below. They can be called the linkedin passport strategy options also.

```typescript
interface LinkedinAuthModuleOptions {
  clientID: string;
  clientSecret: string;
  callbackURL: string;

  scope?: string[] | undefined;
  scopeSeparator?: string | undefined;
  enableProof?: boolean | undefined;
  profileFields?: string[] | undefined;
}
```

### LinkedinAuthModuleAsyncOptions

If you want to configure the `LinkedinAuthModule` dynamically having the config or other services injected, pass in async options in the `forRootAsync` static method. Please refer to the example above for `useFactory` and `useClass` properties.

```typescript
interface LinkedinAuthModuleAsyncOptions {
  useExisting?: Type<LinkedinAuthModuleOptionsFactory>;
  useClass?: Type<LinkedinAuthModuleOptionsFactory>;
  useFactory?: (
    ...args: any[]
  ) => Promise<LinkedinAuthModuleOptions> | LinkedinAuthModuleOptions;
  inject?: any[];
}
```

### LinkedinAuthModuleOptionsFactory

```typescript
interface LinkedinAuthModuleOptionsFactory {
  createModuleOptions():
    | Promise<LinkedinAuthModuleOptions>
    | LinkedinAuthModuleOptions;
}
```

## Have Issues?

If you still have trouble setting up the workflow properly, please file an issue at [Issues](https://github.com/mjangir/nestjs-hybrid-auth/issues) page.

## Maintainers

[Manish Jangir](https://github.com/mjangir)