npmpackage.info

Gathering detailed insights and metrics for serverless-offline-local-authorizers-plugin

serverless-offline-local-authorizers-plugin

Plugin for adding local authorizers when developing locally with serverless-offline

1.2.0

MIT

TypeScript

1.36 kB

1,083,207 2.1

Installations

npm install serverless-offline-local-authorizers-plugin

Pull Requests

Open

2

Total

32

Closed

18

Merged

12

Issues

Open

6

Total

15

Closed

9

Releases

v1.0.3

Published on 04 Sept 2020

View all 1 releases

Developer

nlang

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

Yes

Node Version

14.16.1

NPM Version

8.5.0 Statistics

16 Stars

48 Commits

22 Forks

2 Watching

3 Branches

4 Contributors

Updated on 08 Dec 2023

Bundle Size

3.11 kB

Minified

1.36 kB

Minified + Gzipped

Bundlephobia

Languages

TypeScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

1,083,207

Last day

28.7%

852

Compared to previous day

Last week

15%

4,320

Compared to previous week

Last month

-9.5%

18,090

Compared to previous month

Last year

-11.7%

279,762

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

@types/node typescript

Versions

serverless-offline-local-authorizers-plugin

Serverless plugin for adding authorizers when developing and testing functions locally with serverless-offline.

This plugin allows you to add local authorizer functions to your serverless projects. These authorizers are added dynamically in a way they can be called by serverless-offline but don't interfer with your deployment and your shared authorizer functions. This helps when you have shared API Gateway authorizers and developing and testing locally with serverless-offline.

:warning: If you are using this plugin and get schema validation errors: Please check indentation of localAuthorizer: config property! See example below...

Installation

Installing using npm:

npm i serverless-offline-local-authorizers-plugin --save-dev

Usage

Step 1: Define your authorizer functions in a file of your choice (.js, .mjs, .ts and others) and later you will inform the path and name or file default called local-authorizers.js and put it into your project root (that's where your serverless.yml lives).

If you want the local function to call your deployed shared authorizer it could look something like this:

1const AWS = require("aws-sdk");
2const mylocalAuthProxyFn = async (event, context) => {
3
4  const lambda = new AWS.Lambda();
5  const result = await lambda.invoke({
6    FunctionName: "my-shared-lambda-authorizer",
7    InvocationType: "RequestResponse",
8    Payload: JSON.stringify(event),
9  }).promise();
10
11  if (result.StatusCode === 200) {
12    return JSON.parse(result.Payload);
13  }
14
15  throw Error("Authorizer error");
16};
17
18module.exports = { mylocalAuthProxyFn };
19

Of course you could also just return a mocked response, call Cognito to mock your Cognito Authorizer or whatever suits your needs. You can also define multiple authorizer functions if you need to.

Step 2: In your serverless.yml, add the localAuthorizer property to your http events. This will not interfere with your "real" authorizers and will be ignored upon deployment.

1functions:
2  myFunction:
3    handler: myFunction.handler
4    events:
5      - http:
6          path: /my/api/path
7          method: GET
8          authorizer:
9            type: CUSTOM
10            authorizerId: abcjfk
11          localAuthorizer:
12            name: "mylocalAuthProxyFn"
13            pathFile: "local-authorizers.js" # Optional
14            type: "request"
15

Step 3: Add the plugin to the plugins sections in serverless.yml:

1plugins:
2  - serverless-offline-local-authorizers-plugin
3  - serverless-offline

Step 4: Fire up serverless offline with the local-authorizers option:

1$ sls offline local-authorizers --stage dev --region eu-central-1

License

MIT

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

3

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.1

/10

Last Scanned on 2024-11-18

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More