| Age | Commit message (Collapse) | Author |
|---|
|
Some more constants added to ConfigHelper.
This solves #2908.
|
|
There was a problem on the assets file "bitmask.url". It had an error in
the eip-service url.
We should use this file only for main url, and proceed as if it were a
new provider but with a preseeded main url.
|
|
Allow registration is present in provider.json.
Provider.json is downloaded from both preseeded and custom providers.
Authentication success or fail is notified correctly to the user.
|
|
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.
|
|
Change bitmask eip-service.json url from api/1 to api:4430 (Support
#1759)
|
|
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.
|
|
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
:)
|
|
variety,
And there shady json files...Creates Issue #1593
|
|
|
|
The jniclose method works. But there should be a java way to do it ... (closes issue #12)
|
