-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(aws-cdk/aws-amplify): basicAuth cannot be removed #15028
Comments
Hi @mwiarda-fette, thanks for opening the issue. Do you perhaps have Premium Support? I think this might be worth it to open to the Amplify team directly - looks like their CloudFormation support does not handle edits correctly. Unfortunately, there's not much we can do here from the CDK side. Thanks, |
Hi Adam, thanks for the feedback. Best, |
Removing the `BasicAuthConfig` property from the template doesn't remove the basic auth. Explicitely set `EnableBasicAuth` to `false` instead. Closes aws#15028
Removing the `BasicAuthConfig` property from the template doesn't remove the basic auth. Explicitely set `EnableBasicAuth` to `false` instead. Closes #15028 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Removing the `BasicAuthConfig` property from the template doesn't remove the basic auth. Explicitely set `EnableBasicAuth` to `false` instead. Closes aws#15028 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Removing the `BasicAuthConfig` property from the template doesn't remove the basic auth. Explicitely set `EnableBasicAuth` to `false` instead. Closes aws#15028 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Removing the `BasicAuthConfig` property from the template doesn't remove the basic auth. Explicitely set `EnableBasicAuth` to `false` instead. Closes aws#15028 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Hi,
basicAuth can be enabled on an amplify application using the cdk.
Unfortunately, that setting can not be reversed. The cloudformation template changes but basic auth is still active in amplify.
Reproduction Steps
What did you expect to happen?
Password protection should be removed
What actually happened?
Template changes (shows in cdk diff) but protection not removed in amplify
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: