aws-cognito

I have used the following example to implement AWS Cognito in nodeJS but i am facing the error "'AWSCognito' is not defined no-undef" Reference Link : https://github.com/aws/amazon-cognito-identity-js/ Following is my code in App.js file. I have used react-app. import React, { Component } from 'react'; import logo from './logo.svg'; import './App.css'; import { CognitoUserPool, CognitoUserAttribute, CognitoUser } from 'amazon-cognito-identity-js'; class App extends Component { constructor(props, context){ super(props, context); this.state = { items: [] } } render() { const {items} = this.state

I am trying to figure out how to sign in a User with AWS Cognito. The tutorials all seem to deal with Users from a standpoint of signing up Users, not signing them in. I do not want the users to go through a sign-up process; that will be done elsewhere, by our office users. I just want to have, in this app, a flow that has them enter their existing username and password and sign in. My current understanding of things is that Cognito User Pools only supports either sign-in using an authentication provider like Facebook or Google, or non-authenticated sign-in, which I am having trouble

I know services such as Auth0 can act as both SAML IdPs and integrate with third party IdPs. It would seem that Cognito can only integrate with other third party IdPs as a service provider, it can actually perform the role of an IdP. The use case is we have our apps creating users in Cognito. We'd like to use a third party application which can integrate with a SAML IdP to support SSO. Is this possible with Cognito or would we need to use something like Auth0? Currenlty, Cognito is an OIDC IdP and not a SAML IdP. If an application supports OIDC, you can use Cognito to connect to that. We have

I am trying to use aws api gateway authorizer with cognito user pool. It is working fine when i test using aws api gateway console. But when i try enabling the authorization in the api it says "message": "Unauthorized". Please check below screenshot API Gateway Console Screenshot - This works fine Postman Screen shot - Not working Can someone help please. FYI I have followed the instructions as mentioned here http://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-integrate-with-cognito.html In my case, authorization code should be id_token . I made a mistake for using access

I want to redirect to a specific url after the user confirmation in amazon cognito. When a user sign up he will get confirmation mail with a verification link as follows https://<>.auth.us-west-2.amazoncognito.com/confirmUser?client_id=<<>>&user_name=<<>>&confirmation_code=<<>> If the user clicks the above link it will redirect to confirmation page. Once the user confirmation is completed the page should redirect to my application. Please give me some idea to solve this problem. Currently, this redirection can't be done using verification link in email. I tried adding redirect_uri to the

I'm trying to use Federation from a User Pool . Note, I am not talking about Federated Identity Pool a different concept. Is there a SignIn API for federated users or is just a hosted UI Does the app "have to" open a browser on a Sign In URL that looks like https://XXXXXX.au=th.XXXXX.amazoncognito.com/login?response_type=code&client_id=XXXXXXXXX&redirect_uri=XXXXXXX ? Can the end-user can stay inside the app, similar to how Google SignIn API on Android works (it pops up a small Google sign in UI, user clicks on their name, you're immediately back inside the app with a token. How do I launch a

I'm trying to set up a basic website (serverless on AWS) that would allow visitors to login with Google and/or Facebook. Currently I'm planning to use S3, Cognito with Federated Identities, API Gateway, Lambda (NodeJS), with DynamoDB. The client app will be using Angular. I have the social login with Google and Facebook working, and currently I am inserting a row in a "users" table when a user logs in the first time that includes the cognitoId, name, profile picture URL, etc. I also figure it would be a good design to store the user's information with their email address as the key, instead of