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.
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
I followed all steps and was able to get the token however token is not working when invoking API. getting bellow error: { "message": "Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): 'fsdfdfdf/XXXXXXXewrwfsdfsdfewesdfsdf='." }
Precise to the point fully packed 16 mins. I like the fact that you did not waste time on creating lambda integration :)
Thank you very much. This is a clear tutorial with good explanation. ♥
Glad it was helpful!
Very good video: clear and directed to the point. Thanks
Glad it was helpful!
This is a great video. There are not a lot of resources on this topic. Thanks...!
You are really great. Thank you for the awesome content.
Really pleased I found this video, it's been a huge help.
Thank you so much! Now it is clear
very nice video .
Thank you for this video!
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.
Thank you
is it possible to extend the Cognito configuration to use OIDC (e.g. Azure AD) for machine to machine authorization using JWT token?
Great video, but this aproach is B2B. M2M is by the "device_code" flow.
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
but how can this client secret be kept secure...
I followed all steps and was able to get the token however token is not working when invoking API. getting bellow error:
{
"message": "Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): 'fsdfdfdf/XXXXXXXewrwfsdfsdfewesdfsdf='."
}