Machine to Machine authorization using Client Credentials flow in AWS Cognito and with API Gateway

Поділитися
Вставка
  • Опубліковано 19 сер 2024
  • If you need to do machine to machine authorization with the Client Credentials flow with AWS Cognito then this video is for you. I am going to explain what the client credentials flow looks like and what is it used for. Then we're going to go through the whole process of setting this up with a Cognito User Pool and demo it with API Gateway and Postman.
    If you liked this video please click on the like button! There's a new video on Majestic.cloud once a week so if you want to stay updated and don't want to miss any new videos then please subscribe to the channel!
    Visit the site: majestic.cloud
    Follow me on Twitter:
    / lacisoft (László)
    / cloud_majestic (Majestic.cloud)
    Follow on Facebook: / majesticcloudcomputing
  • Наука та технологія

КОМЕНТАРІ • 9

  • @darkingsky
    @darkingsky 9 місяців тому +2

    Very good video: clear and directed to the point. Thanks

  • @maticase
    @maticase Місяць тому

    This is a great video. There are not a lot of resources on this topic. Thanks...!

  • @johnlowe6894
    @johnlowe6894 2 місяці тому

    Really pleased I found this video, it's been a huge help.

  • @Alina_K137
    @Alina_K137 7 місяців тому +1

    Thank you so much! Now it is clear

  • @PenguinSpdSlayeR
    @PenguinSpdSlayeR 4 місяці тому

    Great video! But only showing auth through postman, people may struggle with a 'machine to machine' requests as the premice of the video made we expect.

  • @pedroprado8295
    @pedroprado8295 6 місяців тому

    Thank you for this video!

  • @francistony7110
    @francistony7110 20 днів тому

    but how can this client secret be kept secure...

  • @vijaykumarmotupalli6912
    @vijaykumarmotupalli6912 3 місяці тому

    I did exactly same but i have multiple app clients for same userpool, one of the client using client credentials flow. If i use same user pool as authorizer it only accepting ID token but not access token so third client generated access token not working