-
Notifications
You must be signed in to change notification settings - Fork 820
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
Social sign in with apple scope, mapping and environment variables #7793
Comments
Is this a bug report for the CLI? If so can you provide steps to reproduce, and describe what you expected vs what you got? As for your comment about the doc site, I believe that page is owned by amplify console, you can open up a ticket with them here |
Yes it is a bug report. The steps to reproduce is:
Then select:
Then tick
Then provide the requested information and finally
The result is what I attached in the previous post and what is expected is this screen shot: Note the first item in the list. In the previous post, email and name are squashed into one item The environment variables are requested here #2118 |
@pedramp20 If you'd like, you can test a fix we've been working on. https://www.npmjs.com/package/@aws-amplify/cli/v/5.3.0-siwa-update.3 |
Thanks for the update. When are you planning to merge the changes into your master branch? As this issue is very annoying in the build pipeline and after each build the settings need to be reconfigured manually @letsbelopez |
* fix(amplify-category-auth): fixes being able to update siwa w/ out private key and attr mapping Cognito SDK takes null for the private key if users want to update everything but the private key and updating to reflect the correct attribute mapping for siwa fix #7793 * fix(amplify-category-auth): enable update siwa w/ out private key Co-authored-by: David Lopez <[email protected]>
👋 Hi, this issue was referenced in the v5.5.0 release! Check out the release notes here https://github.com/aws-amplify/amplify-cli/releases/tag/v5.5.0. |
* fix(amplify-category-auth): fixes being able to update siwa w/ out private key and attr mapping Cognito SDK takes null for the private key if users want to update everything but the private key and updating to reflect the correct attribute mapping for siwa fix aws-amplify#7793 * fix(amplify-category-auth): enable update siwa w/ out private key Co-authored-by: David Lopez <[email protected]>
* fix(amplify-category-auth): fixes being able to update siwa w/ out private key and attr mapping Cognito SDK takes null for the private key if users want to update everything but the private key and updating to reflect the correct attribute mapping for siwa fix #7793 * fix(amplify-category-auth): enable update siwa w/ out private key Co-authored-by: David Lopez <[email protected]>
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Recently sign in with apple option is added to the supported options in CLI (5.1.2). The hostedUIProviderMeta parameter is generated as follows:
This authorisation scope for sign in with apple is comma separated and attribute mapping is missing name to name and sub to username maps, this results in a weird configuration of the federation identity provider and mapping (a record with email,name is added on the top) in console and when redirected to Apple throws an error of "Invalid client scope"
If the checkboxes of the authorisation scope is unticked and ticked and saved in the console, the issue goes away.
The console environment variables page does not specify the default variables for sign in with apple either. Please update it.
https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html
The text was updated successfully, but these errors were encountered: