Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corrected path of user and token functions #692

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Corrected path of user and token functions #692

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _examples/how-to-add-github-login-to-your-cognito-user-pool.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ export async function handler() {
}
```

{%change%} Add a `services/token.ts`.
{%change%} Add a `services/functions/token.ts`.

Requesting data from the token endpoint, it will return the following form: `access_token=xxxxxxxxxxxxxxxxxxxxxxx&token_type=bearer`, which is not a JSON. It should be returning a JSON object for OpenID to understand. The below lambda does exactly that.

Expand Down Expand Up @@ -214,7 +214,7 @@ Make sure to install the `node-fetch` and `lambda-multipart-parser` packages.
npm install node-fetch lambda-multipart-parser
```

{%change%} Add a `services/user.ts`.
{%change%} Add a `services/functions/user.ts`.

User info endpoint uses a different authorization scheme: `Authorization: token OAUTH-TOKEN`. But, OpenID will send a `Bearer` scheme so that's we need a proxy to modify it to correct scheme.

Expand Down