I am facing an issue while submitting the form, although I have done all those steps to add antiforgery token but still it is throwing error as below:-
An unhandled exception occurred while processing the request.
FormatException: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.
System.Convert.FromBase64CharPtr(Char* inputPtr, int inputLength)
AntiforgeryValidationException: The antiforgery token could not be decrypted.
Microsoft.AspNetCore.Antiforgery.DefaultAntiforgeryTokenSerializer.Deserialize(string serializedToken)
I am stuck and need help here to fix this ASAP as this is stalled my major work.
Many thanks for your reply but thing is that I am getting this issue on my local environment. Also, on Azure we have only single instance. But still this issue persists.
Umbraco Forms Antiforgery Token issue
I am facing an issue while submitting the form, although I have done all those steps to add antiforgery token but still it is throwing error as below:-
An unhandled exception occurred while processing the request. FormatException: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters. System.Convert.FromBase64CharPtr(Char* inputPtr, int inputLength)
AntiforgeryValidationException: The antiforgery token could not be decrypted. Microsoft.AspNetCore.Antiforgery.DefaultAntiforgeryTokenSerializer.Deserialize(string serializedToken)
I am stuck and need help here to fix this ASAP as this is stalled my major work.
do you have multiple servers? if yes you need sync key storage or machine key, depend on version
https://learn.microsoft.com/en-us/aspnet/core/security/data-protection/implementation/key-storage-providers?view=aspnetcore-8.0&tabs=visual-studio
Hello Yakov,
Many thanks for your reply but thing is that I am getting this issue on my local environment. Also, on Azure we have only single instance. But still this issue persists.
is working on a reply...