SandroB forgot that certificate was already installed and would no longer work

[GoogleCodeExporter]

I DON"T KNOW WHERE ELSE TO POST A QUESTION ON USING CERTIFICATES WITH SANDROB 
SO I POST MY QUESTION HERE:
  My company requires use of a certificate (.p12 file) to get to company websites and I was able to install it into SandroB for Android 2.3.4 with the certificate installed in 'local store'. I deleted the certificate file on the phone for security since many apps ask for read/write priviledge on the sdcard.   However, the next time I wanted to use it, SandroB forgot it was already installed and would no longer work.  I reinstalled, things worked again, and then it again forgot everything a few days later. HOW CAN I MAKE SANDROB RETAIN THE CERTIFICATE INFORMATION IN LOCAL STORE, as it is a big pain to have to read in the location of the file all the time and give its password, especially when I don't think it is safe to leave the certificate file on the SDDISK.  
  Thank you very much for your help and please take into account I know very little about how these things are supposed to work; just that I need it to get to certain URL's.
-Jeff

Original issue reported on code.google.com by supp.san...@gmail.com on 17 Jan 2012 at 8:25

[GoogleCodeExporter]

So far there were no reports of that kind of behavior.
Reasons that certificate is deleted from SandroB local store:

- too many wrong passwords (3)
- !! every time when popup aprears if you uncheck "local store" checkbox !!
- Application->Manage Applications->SandroB->Clear data
- sometimes servers optionally requests client certificates just for the part 
of  
  hosted urls. Use then SandroB->Menu->Settings->SSL dialog only on errors = OFF

http://code.google.com/p/sandrob/wiki/CertificateLocalStore

If above reasons are not your case please send some more information.

Original comment by supp.san...@gmail.com on 17 Jan 2012 at 8:49

[GoogleCodeExporter]

Since it worked fine this morning before I was about to reinstall a new copy of 
the certificate and since I probably did have 3 wrong passwords at least one of 
the two times this happened (pretty sure not the second time), this sounds may 
have been cockpit error on my part.  I'll keep using it to see if it occurs 
again and, if so, try to collect information.  
  It is good to hear that, once installed in local store, it SHOULD be retained.
Thanks,
Jeff

Original comment by jeffwei...@gmail.com on 17 Jan 2012 at 3:35

[GoogleCodeExporter]

Unfortunately, I continue to get erratic unpredictable behavior; sometimes it 
works and then it doesn't. Very frustrating.
  When it was working I could go to all 3 sites I need to with the stored certificate (which I had deleted from sdcard for security).  Next time I try to go to one of the sites a bit later, It offers two options: enter the file location (again) or choose the certificate that I see in the dialog window and enter the password for it.  I do the latter, but instead of working, it says 'failed attempt'.  After a couple of tries at that and one of the other URL's in question, it says 'too many failed attempts' and proceeds to 'delete stored certificate' and then, if that wasn't enough 'delete certificate' from the disk (although I had already done that).  Seems designed to drive me crazy.  Since I do need to access these URL's when on travel, I would like to know how to get SandroB to behave reasonably and permanently remember the stored certificate, once it says it has successfully installed it.  What can I do?
Thanks
-Jeff

Original comment by jeffwei...@gmail.com on 18 Jan 2012 at 3:39

[GoogleCodeExporter]

...after reinstalling the certificate in local store from disk, I get another 
failure variant (I've seen at least three different ones so this is #2):
Successfully accessing one URL which has links to the other two, when I hit one 
of those links, it asks for password only, but won't accept the password 
('failed attempt').  I successfully go back to the first URL and try clicking 
on link to the third URL but this time I get what I described in the previous 
message: a dialog box with the two choices of entering a file location or 
choosing a certificate that is listed there and is clearly my certificate. When 
I choose the second option, however,and enter the password for the certificate, 
of course, it fails again although I didn't record the exact wording of the 
failure.
  Tried this again a few minutes later and I could again access all 3 URL's, although one of them gave the two-choice dialog but this time accepted my same password for the second option using the certificate I can see (and I checked local store this time, which I don't remember seeing or doing the previous time).
  Maybe some step-by-step instructions for the nonprogrammer/user might help me.
-Jeff

Original comment by jeffwei...@gmail.com on 18 Jan 2012 at 4:06

[GoogleCodeExporter]

I will try to replay your scenarios (3 sites for the same client certificate) 
and see if I can find any problems.

The main problem seems to be in 'failed attempts'. 
This cause all other problems with pop-ups.
Maybe reason are some special characters in password 
so I will test those too more firmly.

But if it is possible, can you try for a day of use 
some simple plain password for which you can be sure that it is not miss-typed?

http://code.google.com/p/sandrob/wiki/MultipleSSLsessions
In your case there are three ssl contexts.
So you should see three pop-ups at the beginning of use.
With no failed attempts.

Original comment by supp.san...@gmail.com on 18 Jan 2012 at 8:36

[GoogleCodeExporter]

Thanks. Ok, I'm using a straight number password and I was able to access all 
three URL's (each set as a bookmark) several times (each wanted a password the 
first time); then click on links in the primary URL to the other two and return 
successfully without it asking for a password.  So maybe it was a problem of 
successfully entering the password.  This seems to be working for me now.  
Hopefully, I'm in business now.
Thanks,
-Jeff

Original comment by jeffwei...@gmail.com on 19 Jan 2012 at 6:52

[GoogleCodeExporter]

I'm glad that you make it work.
Were there any special character in previous passwords that should be tested?
Otherwise this issue will be closed.

Original comment by supp.san...@gmail.com on 19 Jan 2012 at 9:25

[GoogleCodeExporter]

Just straight numerical but was much more careful entering on the phone (HTC 
Sensation 4G).  Seems to be working consistently now.
Tnx.
-Jeff

Original comment by jeffwei...@gmail.com on 20 Jan 2012 at 5:15

[GoogleCodeExporter]

Original comment by supp.san...@gmail.com on 20 Jan 2012 at 8:16

• Changed state: WontFix