summaryrefslogtreecommitdiff
path: root/assets/urls/bitmask.url
AgeCommit message (Collapse)Author
2013-04-29"Trust completely" checkbox saves that trust for the new providerParménides GV
entered, so that if in the future the client tries to log in or whatever, it can use the certificate downloaded when added. Log in dialog works ok, showing a toast when authentication fails (by this time, I have not managed to get a correct login due to dev.bitmask.net problems). dev.bitmask.net works perfectly, via adding it as a new provider (MeanderingCode, this is for you ;) ). All GET requests are done by default Android URL class, which means that certificates trusted by Android are also trusted by us. If there are problems when logging in due to certificates, the app is able to use only the certificate associated to the provider in the moment it was selected as the chosen provider.
2013-02-26Resolved issue:Parménides GV
Change bitmask eip-service.json url from api/1 to api:4430 (Support #1759)
2013-02-05Simplified certificates and urls: only 1 certificate, and no :443 portParménides GV
in eip. Downloads certificate and eip from web, and loads provider from assets. KeyStore not created with latest version of BouncyCastle. Looking forward to file a bug and look for a solution.
2013-01-31Problems with downloaded file, the emulator cannot find the fileParménides GV
downloaded. Seen http://code.google.com/p/android/issues/detail?id=18462 and decided to look for another solution. First solution thought (and going to be the next test): HTTP Get request :)