| Age | Commit message (Collapse) | Author |
|---|
|
It is stored in SharedPrefs, with ConfigHelper.cert_key (="cert") key.
|
|
certificate.
Next step in this branch: detect what the selected provider support in
terms of authenticated/anon users, and show login/logout methods
consecuently.
|
|
The problem was that I needed to append the api_version to the api_uri.
I was doing well in tests because I hardcoded the api urls, but in
production code I was getting from provider.json only api_url and not
api_version.
|
|
request a log in without certificates problems.
I've removed the addition of the certificate when downloaded
eip-service.json, because I already do that in LeapHttpClient.
Solves issue 2367: https://leap.se/code/issues/2367
|
|
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.
|
|
|
|
I need to implement bypass for dev.bitmask.net, because bitmask.net is
down.
|
|
|
|
|
|
|
|
had ProviderList stuff)
|
|
have no config (createed NullPointerExceptions)
|
|
|
|
the saveSharedPrefs method and an unimplemented rescueFromJSONException.
Next step: managing HttpsURLConnection for the
CertPathValidatorException.
|
|
eip-service.json file.
provider.json downloads and parses itself OK to SharedPreferences.
It also does not link OK to the Dashboard, I do not know how to do it
properly and I'm so tired (eyes hurting).
Beginning with security things :) Happy to have gotten around
DownloadManager problem with a simple HTTP connection.
|
|
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
:)
|
|
Added parts to expand listing for quick info and settings access
|
|
|
|
variety,
And there shady json files...Creates Issue #1593
|
|
Needs attention, as the AboutFragment does not fill the layout
You can still see providerLine
Creates Issue #1592
|
|
Matching layout and menu XML
And don't forget strings
|
|
|
