AWS re:Invent 2017: [REPEAT] Serverless Authentication and Authorization: Identity M (SRV403-R)

Поделиться
HTML-код
  • Опубликовано: 30 июл 2024
  • Many serverless applications need a way to manage end user identities and support sign-ups and sign-ins. Join this session to learn real-world design patterns for implementing authentication and authorization for your serverless application-such as how to integrate with social identity providers (such as Google and Facebook) and existing corporate directories. We cover how to use Amazon Cognito identity pools and user pools with API Gateway, Lambda, and IAM.

Комментарии • 13

  • @VladimirOdessit
    @VladimirOdessit 6 лет назад +3

    The app that we referenced during the talk: github.com/awslabs/aws-serverless-auth-reference-app
    Here's a sample single-page web-app written in Angular using Cognito and running on S3 (completely serverless):
    github.com/awslabs/aws-cognito-angular-quickstart
    Serverless Photo Recognition using most of the services we talked about, in addition to Amazon Rekognition:
    github.com/awslabs/serverless-photo-recognition
    Blog post:
    aws.amazon.com/blogs/ai/use-amazon-rekognition-to-build-an-end-to-end-serverless-photo-recognition-system/

    • @danielpapukchiev3754
      @danielpapukchiev3754 6 лет назад

      Hello, we are using Cognito Federated Identities for Facebook and Google auth and Cognito Userpools for username/password flows. Our back-end is a serverless API with API Gateway. To protect it we wanted to use aws_iam authorizer but we reached a problem. To refresh aws keys with Cognito Federated Identities we have to supply the original Facebook/Google/Cognito tokens which also expire in a short period of time. How would a user coming from Facebook for example refresh his/hers AWS keys given from Cognito federated identities? In the end we decided to issue our own JWT tokens with refresh tokens via DynamoDB + custom lambda authorizers which validate those tokens, so all users go trough the same refresh flow apposed to using each identity provider refresh mechanism in the front end.

    • @VladimirOdessit
      @VladimirOdessit 6 лет назад

      Take a look at this documentation: docs.aws.amazon.com/cognito/latest/developerguide/cognito-identity.html

  • @NS38845
    @NS38845 6 лет назад +14

    I like how you numbered this 403

  • @michaelchambers236
    @michaelchambers236 6 лет назад +2

    Thank you both. Great presentation and very helpful!

  • @gummibare
    @gummibare 6 лет назад +10

    Why is it that AWS passes the ID token to retrieve credentials from Federated Identities? Specifically at 9:50. Isn't Access Token the ideal token to use in this case, since it twas specifically meant for providing access to APIs?

  • @elritualk
    @elritualk 5 лет назад

    Hi, first thanks for this overview. I have a question: User Pool -> Federation cost money based on MAU and Federated Identity is free no matter what MAU you have?

  • @gireeshkumarmn2796
    @gireeshkumarmn2796 5 лет назад +2

    Awesome! content and the best one to get started with cognito.

  • @selimcse98
    @selimcse98 5 лет назад +1

    Can you please share the application source code?

    • @hoangedward
      @hoangedward 5 лет назад

      Mohammad Selim Miah at the end of video