Okay, thanks for the explanations. But what I was waiting for is this: * User (not yet signed in) uses the web browser (e.g. Firefox) and calls a URL that is protected. * Then I want the login dialogue to pop up (the one that you used in the Cognito pool to sign in) and the user can enter credentials. * When credentials are okay, then the browser proceeds to the protected URL and shows the content. So how do I achieve this? What you were explaining seems to be going on below the surface. I cant expect my users to manually launch the hosted UI from the AWS console... they dont have access to the account where the pool is in...?!
Hello Ravi, thanks for this video session. I have one query. When we have only read only scooe, how aws cognito knows that post operation is not allowed
Okay, thanks for the explanations. But what I was waiting for is this:
* User (not yet signed in) uses the web browser (e.g. Firefox) and calls a URL that is protected.
* Then I want the login dialogue to pop up (the one that you used in the Cognito pool to sign in) and the user can enter credentials.
* When credentials are okay, then the browser proceeds to the protected URL and shows the content.
So how do I achieve this? What you were explaining seems to be going on below the surface. I cant expect my users to manually launch the hosted UI from the AWS console... they dont have access to the account where the pool is in...?!
great video, thaks a loooot
Hello Ravi, thanks for this video session. I have one query. When we have only read only scooe, how aws cognito knows that post operation is not allowed
I mean, what if I use same scope defined in RS, for POST method.