Skip to content
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

Umbraco throws Authorization error after marking a field as non sensitive data #976

Closed
RGV2ZWxvcGVy opened this issue Feb 14, 2023 · 5 comments

Comments

@RGV2ZWxvcGVy
Copy link

Whenever a field in Umbraco Forms is marked as sensitive data you can save the form without any problems. However if you remove the sensitive data flag from this same field, Umbraco throws an Authorization error after saving the changes.

This issue can be reproduced by using a clean install of Umbraco 10.4.0 with Umbraco Forms 10.2.3.

  1. Create a new form
  2. Mark a field as sensitive data
  3. Save the changes
  4. Uncheck the sensitive data toggle on a field
  5. Submit the changes

image

@AndyButland
Copy link

Thanks for the report, can replicate. We'll get this fixed up for the next releases.

@RGV2ZWxvcGVy
Copy link
Author

@AndyButland Do you happen to know if there is a workaround to uncheck the sensitive data flag on a field without recreating the entire form?

@AndyButland
Copy link

Not that I can see from a UI or code perspective I'm afraid - it seems there was simply a bug in a check used to determine if the current user is allowed to remove this flag based on their permissions, that we'll need to patch.

The only option I can see would be to - carefully! - update the information on the form directly in the database - it's in the UFForms table, there's a field called Definition that contains the JSON representation of the form details. You'll find this flag on the field and could update the value.

@RGV2ZWxvcGVy
Copy link
Author

@AndyButland Okay thanks for the info!
Is there any news on when version 10.2.4 of Umbraco Forms is gonna get released? Or could this take a few weeks?

@AndyButland
Copy link

Not scheduled yet, but in the next 2-3 weeks I expect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants