oauth 2.0 - Client app authorization for AWS API Gateway -


i'm trying figure out best way deploy api in amazon api gateway. i'm getting totally confused appropriate authorization use.

the api used our customers own custom developed apps.

we don't need provide end user authentication. handled on our customers, based on specific requirements apps.

what need do, provide way our customers apps authenticate against our api.

my understanding have following options...

  1. aws_iam - may not appropriate, adding customer credentials our amazon account.
  2. cognito user pool authorizer - seems designed user authorization, rather client authorization.
  3. custom authorizer - presumably can tailored our specific requirements, need lot of code built scratch.
  4. api key authentication - quick , easy, doesn't seem particularly secure, rely on key header.

i had assumed, there straightforward way enable oauth2 authentication. our use-case, "client credentials" flow have been suitable. research i've done, sounds oauth2 authentication require custom authorizer lambda. i'm not keen on idea of having implement full oauth2 service, authenticate app. cost build this.

also if we're writing our own full custom oauth2 authorizer, , writing of functionality api itself, i'm not sure how api gateway providing value.

is there best practice, or standard authenticating api clients api gateway?

what need doesn't seem particularly unusual thing, there must standard way people this.

any suggestions appreciated.


Comments

Popular posts from this blog

angular - Ionic slides - dynamically add slides before and after -

minify - Minimizing css files -

Add a dynamic header in angular 2 http provider -