Merge pull request serverless#309 from BrianAndersen78/patch-1

eahefnawy · web-flow · commit 3db81d5ed3f3 · 2018-10-18T14:36:27.000+03:00
Update readme.md
diff --git a/aws-python-auth0-custom-authorizers-api/README.md b/aws-python-auth0-custom-authorizers-api/README.md
@@ -42,22 +42,25 @@ Custom Authorizers allow you to run an AWS Lambda Function before your targeted
 
 7. You can either run your frontend locally or deploy your frontend to host of your choosing. However in either case, make sure to configure the `Allowed Callback URL` and `Allowed Origins` in your auth0 client in the [auth0 dashboard](https://manage.auth0.com). An example of how to run your frontend locally:
 
-  ```cd frontend;
-  python -m http.server```
+  ```
+  cd frontend;
+  python -m http.server
+  ```
 
 
 ## Custom authorizer functions
 
 [Custom authorizers functions](https://aws.amazon.com/blogs/compute/introducing-custom-authorizers-in-amazon-api-gateway/) are executed before a Lambda function is executed and return an Error or a Policy document.
 
-The Custom authorizer function is passed an `event` object as below:
+The Custom authorizer function is passing an `event` object to API Gateway as below:
 ```javascript
 {
   "type": "TOKEN",
   "authorizationToken": "<Incoming bearer token>",
   "methodArn": "arn:aws:execute-api:<Region id>:<Account id>:<API id>/<Stage>/<Method>/<Resource path>"
 }
 ```
+You will have to change this policy to accommodate your needs. The default reply provided, will only authorize one endpoint!
 
 ## Frontend
 
