summaryrefslogtreecommitdiff
path: root/src/se/leap/leapclient/LogInDialog.java
AgeCommit message (Collapse)Author
2013-07-26Include GPLv3+ file and header for files in se.leap.leapclient packageSean Leonard
2013-07-12User messages are added to the new recovery dialogParménides GV
When login is not successful, a new recovery dialog is prompted with a message about the previous error.
2013-07-12Use anonymously from ProviderDetail works OK.Parménides GV
Tested with dev.bitmask.net, I use the previously downloaded certificate (I should not do that, I'll file an issue because I should download it once the user has requested to do so). Next step: login button from ProviderDetailFragment.
2013-07-12Coded new fragment appearanceParménides GV
Domain, name and description come from provider.json Next step: code buttons to login or to use anonymously.
2013-06-20User messages are now in string.xmlParménides GV
Some more constants added to ConfigHelper. This solves #2908.
2013-06-19First round of comments.Parménides GV
This resolves the first step from issue #2908. Next step: Put user message strings into an appropiate place.
2013-06-08Clean up some unused and some formattingSean Leonard
2013-06-08Make LogInDialog accept passwords >= 8 characters, instead of > 8Sean Leonard
2013-05-13A bit more clean.Parménides GV
I've upper cased ConfigHelper constants. I've created a new method in ConfigHelper, to send requests to a server, that it's used when sending A and M1.
2013-04-29Changed the message shown when checking if the password is valid or not.Parménides GV
Refactored LeapSRPSession so that there is no need to send A twice.
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-04-29Added danger mode: we can bypass dev.bitmask.net hostname io exception.Parménides GV
2013-04-29Coded dialog (now there is a button in the Dashboard), time to test.Parménides GV
I need to implement bypass for dev.bitmask.net, because bitmask.net is down.