-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cognito identity provider's atrribute mapping keeps changing, causing error in triggers. #9016
Comments
Hi @artidata, updating amplify resources outside CLI is not supported. Closing the ticket as per no steps to reproduce. Please reopen if you find a way to reproduce the issue. |
I think it's this line in "hostedUIProviderMeta": "[{\"ProviderName\":\"Google\",\"authorize_scopes\":\"openid email profile\",\"AttributeMapping\":{\"email\":\"email\",\"username\":\"sub\"}}]", That keeps overriding my cognito Attribute mapping set up. However, no cli input can actually override these values. |
Yeap, this line override my cognito oauth attribute mapping setup. I can rewrite it manually, but everytime I am running cli command |
Hi @artidata, I am also having this problem. Have you tried to use amplify override ? Maybe you can customize attribute mappings for your user pool? @lazpavel do you think it is a good idea? |
any update? this behavior really break our team collaboration on the same env as it changes the Cognito attribute whenever we run 'amplify push xxx'. |
ditto |
Any update on this or do I need to open a new issue? |
Before opening, please confirm:
How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
7.4.5
What operating system are you using?
Ubuntu
Amplify Categories
auth
Amplify Commands
update
Describe the bug
Cognito atrribute mapping keeps changing. When using identity provider Oauth 2.0 like Google and Facebook. You can configure the Attribute mapping in your cognito console. After setting it up, I will use these attributes in my cognito triggers, such as custom user pool attributes. However, in production all of a sudden attribute mapping change,
name
,picture
,email_verified
no longer mapped. This will prevent user sign up and sign in while in production.Expected behavior
The attribute mapping doesn't change, so my cognito triggers can run smoothly.
Reproduction steps
I have tried many ways to reproduce the bugs. I have tried isolating auth update and do the
amplify push
. But the attribute mapping doesn't change, So yeah, I can't find it. But I am very certain it is there. It will always show up when I am trying to do a product demo. So yeah, that's a painful bug.GraphQL schema(s)
# Put schemas below this line
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: