Skip to Content (Press Enter)
UserImage.jpg
Hans Hol
5580Views
10Comments
Solved
[CryptoAPI] Decrypt - Invalid length for a Base-64 char array or string.
Question
Forge
cryptoapi
Service icon
CryptoAPI (O11)
Forge asset by João Barata

Hi,

I'm using EncryptAES256 to encrypt some data. Then an e-mail is send, with an activation link (with parameter the encrypted string). When I decrypt the string on the screen (of the activation link), I get an error as mentioned in the title.

I checked that the generated string, the string in the link and the string passed to the decrypt are all the same (btw, it ends with an "=").

Few days ago it worked, but now I only get this error.

I searched the internet, but could not find a solution for this perticular situaton.

Any ideas?

 

0
0
23 Nov 2016
Copy Link
2014-02-13 10-06-38
Ricardo Silva
Solution

There you go.

That's your issue. The + is being dumped directly to the URL which means it will be converted to a space. This is just how URL encoding works.

I recommend that you EncodeUrl() the value when generating the URL, or that you use the platform's functionality to create links instead of doing it by hand. By using a Destination node the URL should be properly encoded.

See solution in context
2
0
23 Nov 2016
Copy Link
UserImage.jpg
Hans Hol

Ricardo Silva wrote:

There you go.

That's your issue. The + is being dumped directly to the URL which means it will be converted to a space. This is just how URL encoding works.

I recommend that you EncodeUrl() the value when generating the URL, or that you use the platform's functionality to create links instead of doing it by hand. By using a Destination node the URL should be properly encoded.

ok, i'll try that and let you know if it works. 


Thanks already for your help!


1
0
23 Nov 2016
Copy Link
UserImage.jpg
Hans Hol

Hans Hol wrote:

Ricardo Silva wrote:

There you go.

That's your issue. The + is being dumped directly to the URL which means it will be converted to a space. This is just how URL encoding works.

I recommend that you EncodeUrl() the value when generating the URL, or that you use the platform's functionality to create links instead of doing it by hand. By using a Destination node the URL should be properly encoded.

ok, i'll try that and let you know if it works. 


Thanks already for your help!


Hi,

The Encode part works! 

I'm not sure about your other solution using the lplatform to make a link. Because the link is put in an e-mail and is fired from that e-mail, I'm not sure if this works. E.g. what to do with the different environments the link has to consider (otap). If you like you can inform me, but for now I'm happy with the other solution.


1
0
01 Dec 2016
Copy Link
2014-02-13 10-06-38
Ricardo Silva

"the string in the link and the string passed to the decrypt are all the same"

Are they the same as the string that was output by the encrypt function ?

0
0
23 Nov 2016
Copy Link
UserImage.jpg
Hans Hol

Ricardo Silva wrote:

"the string in the link and the string passed to the decrypt are all the same"

Are they the same as the string that was output by the encrypt function ?

yes they are (at least... I checked the first 3 and the last 3 characters...)


0
0
23 Nov 2016
Copy Link
2014-02-13 10-06-38
Ricardo Silva

Was just re-reading that you also verified that the generated string is the same.


Could you paste one string that's being generated and getting that error here?

0
0
23 Nov 2016
Copy Link
UserImage.jpg
Hans Hol

sure

from the encrypt:

d+RH5IYMuEJ1n/GixDnRbifwDJ1+c5dBLrol/hjChHdj8H5mdbohyPwo0o09VWirgnXbJN6RPINkuSlcnBxGC1LFxlKATfnstoCptJF6OBI=

link in e-mail:

d+RH5IYMuEJ1n/GixDnRbifwDJ1+c5dBLrol/hjChHdj8H5mdbohyPwo0o09VWirgnXbJN6RPINkuSlcnBxGC1LFxlKATfnstoCptJF6OBI=

passed to the decrypt:

d RH5IYMuEJ1n/GixDnRbifwDJ1 c5dBLrol/hjChHdj8H5mdbohyPwo0o09VWirgnXbJN6RPINkuSlcnBxGC1LFxlKATfnstoCptJF6OBI=


+++> I see now that the second character is changed from a "+" to a space???


Message:
Invalid length for a Base-64 char array or string.
Environment InformationeSpaceVer: 388 (Id=93783, PubId=116430, CompiledWith=9.1.300.0)
RequestUrl: https://os-zakelijk-dev.ee.intern/ToonBuildings_Klant/ActivateAccount.aspx?Activate=d+RH5IYMuEJ1n/GixDnRbifwDJ1+c5dBLrol/hjChHdj8H5mdbohyPwo0o09VWirgnXbJN6RPINkuSlcnBxGC1LFxlKATfnstoCptJF6OBI= (Method: GET)
AppDomain: /LM/W3SVC/1/ROOT/ToonBuildings_Klant-40-131243743034245634
FilePath: F:\Applic\OutSystems\Platform Server\running\ToonBuildings_Klant\ActivateAccount.aspx
Locale: en-US
DateFormat: yyyy-MM-dd
PID: 13856 ('w3wp', Started='11/23/2016 7:06:56 AM', Priv=747Mb, Virt=18291Mb)
TID: 38
Thread Name:
.NET: 4.0.30319.42000
Stack:
Invalid length for a Base-64 char array or string.
   at ssToonBuildings_Klant.RssExtensionCryptoAPI.MssDecryptAES256(HeContext heContext, String inParamCiphertext, String inParamPassword, String& outParamPlaintext)
   at ssToonBuildings_Klant.Flows.FlowMainFlow.ScrnActivateAccount.Preparation(HeContext heContext)
   at ssToonBuildings_Klant.Flows.FlowMainFlow.ScrnActivateAccount.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

0
0
23 Nov 2016
Copy Link
2014-02-13 10-06-38
Ricardo Silva
Solution

There you go.

That's your issue. The + is being dumped directly to the URL which means it will be converted to a space. This is just how URL encoding works.

I recommend that you EncodeUrl() the value when generating the URL, or that you use the platform's functionality to create links instead of doing it by hand. By using a Destination node the URL should be properly encoded.

2
0
23 Nov 2016
Copy Link
UserImage.jpg
Hans Hol

Ricardo Silva wrote:

There you go.

That's your issue. The + is being dumped directly to the URL which means it will be converted to a space. This is just how URL encoding works.

I recommend that you EncodeUrl() the value when generating the URL, or that you use the platform's functionality to create links instead of doing it by hand. By using a Destination node the URL should be properly encoded.

ok, i'll try that and let you know if it works. 


Thanks already for your help!


1
0
23 Nov 2016
Copy Link
UserImage.jpg
Hans Hol

Hans Hol wrote:

Ricardo Silva wrote:

There you go.

That's your issue. The + is being dumped directly to the URL which means it will be converted to a space. This is just how URL encoding works.

I recommend that you EncodeUrl() the value when generating the URL, or that you use the platform's functionality to create links instead of doing it by hand. By using a Destination node the URL should be properly encoded.

ok, i'll try that and let you know if it works. 


Thanks already for your help!


Hi,

The Encode part works! 

I'm not sure about your other solution using the lplatform to make a link. Because the link is put in an e-mail and is fired from that e-mail, I'm not sure if this works. E.g. what to do with the different environments the link has to consider (otap). If you like you can inform me, but for now I'm happy with the other solution.


1
0
01 Dec 2016
Copy Link
UserImage.jpg
Keerthi MGS

Hey Hans,


Can u please explain me how did you fixed that issue. I am facing the same issue

invalid length for a Base-64 char array or string.

Thanks,

Keerthi

0
0
29 Nov 2018
Copy Link
2020-06-02 15-25-40
Jordy Heijnen

Hey,

I've used the EncryptAES256 en DecryptAES256 methods to encrypt plaintext, sent the encrypted text to another server via REST api call and decrypt on the other server.

Here, I ran into the same problem: The REST api calls converted all '+' characters to empty spaces ' '. The suggested solution to use EncodeURL() function did not work since other character in the encrypted text like '/' were wrongfully converted.

In the end I just did a replace for the spaces to +, so

Replace(EncryptedText, " ", "+") 

before decryption and this worked for me.

Hope this helps.


Kind regards,

Jordy Heijnen

2
0
08 Mar 2019
Copy Link
2024-08-01 04-11-43
Maki Gurapo

Hi @Jordy Heijnen,


Thank you very much! 

0
0
12 Jan 2024
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.