[TIMOB-27373] Allow p12 password field to accept special characters without escaping
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | n/a |
Status | Open |
Resolution | Unresolved |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | n/a |
Labels | n/a |
Reporter | Zachary Litten |
Assignee | Eric Merriman |
Created | 2019-06-12T19:14:05.000+0000 |
Updated | 2019-09-02T16:46:00.000+0000 |
Description
I recently needed to update my iOS push notification certification. When uploading my exported certification it kept repeatedly stating that the wrong password was being used. Even though I was directly copy-pasting the password that was made from the password generator. Still the same thing after typing the long string in manually, and a couple more times just to be sure it wasn't my own error. I eventually learned that in order for the password field to take my password I had to escape the "$" that was in my password.
So for example, if my password was "pa$sword" in order to input it into the field I had to escape it like so before it would take it: "pa\$sword". I found it a little surprising considering it is a password field. I feel like the form field should be updated or mention having to escape special characters in the [documentation here](https://docs.axway.com/bundle/Titanium_SDK_allOS_en/page/configuring_push_services.html#Configuringpushservices-ConfiguringpushservicesforiOSdevices) to prevent confusion of other users.
Hello [~zlitten], Thanks for reporting this issue. Actually, there is no restriction and no known character limitations for adding password on .p12 certificate. We are investigating on this issue and back to you soon with some updates. Thanks
Hello! Hope you are doing fine today.Would you please reply us regarding previous reviews? We are looking forward to your response.
Hello Rakhi, I do not understand what is exactly being asked of me, but I am happy to assist in any way!
If what Fazlul is saying is correct, that there are no character limitations on the field in the Dashboard, then I think that this issue may be a red herring for you guys. The problem may have arose from Apple's tool which creates the password when exporting the certificate to a .p12 file.
Hello [~zlitten], We have deployed a fix for this issue. Hopefully the fix this will be active very soon. We will update you once done. Thanks.