- 05 Feb, 2015 1 commit
-
-
chriadam authored
Previously, we used g_debug to log the CredentialsNeedUpdate event, but g_debug output is suppressed by default. This commit changes it to use g_message instead, which is not suppressed, to ensure that the event shows up in the journal logs. This commit also suppresses some warnings by switching to newer API to avoid deprecation warnings, and marking some function parameters as unused.
-
- 31 Jul, 2014 1 commit
-
-
Slava Monich authored
Caused by deallocating static memory (hash keys pointing to static strings)
-
- 20 May, 2014 1 commit
-
-
John Brooks authored
-
- 20 Dec, 2013 2 commits
-
-
John Brooks authored
This is not relevant for our accounts architecture, and calling request_password is harmful.
-
John Brooks authored
Unfortunately, telepathy's AuthenticationFailed error arrives for many normal cases, like a connection reset during authentication. We cannot invalidate credentials indiscriminately. Instead, watch for the two specific wocky errors that indicate the server probably rejected our credentials and signal only for those.
-
- 10 Dec, 2013 2 commits
-
-
chriadam authored
Previously, the CredentialsNeedUpdate flag would be set in a variety of situations, including when a generic OperationFailed error occurred. This commit ensures that it is only set for an account when a UserInteraction error occurs (that is, the account credentials are valid but need to be refreshed manually by the user).
-
chriadam authored
Instead, set it on the service which we're using for the account. Also, print a debug line to the log when raising the flag.
-
- 22 Nov, 2013 1 commit
-
-
John Brooks authored
libsailfishkeyprovider is a privileged resource, so we need to launch via the booster to gain privileges. Some careful systemd work related to mission-control-5 will be done to make sure that booster-generic is alwyas available when necessary.
-
- 15 Oct, 2013 1 commit
-
-
chriadam authored
This commit adds a flag to the account which describes which software component raised the "CredentialsNeedUpdate" flag. This allows us to determine more easily whether the flag is an old or new flag, depending on provenance.
-
- 27 Sep, 2013 1 commit
-
-
John Brooks authored
Fixes signon with some services (e.g. google) that require ClientSecret for refreshing tokens.
-
- 24 Sep, 2013 2 commits
-
-
John Brooks authored
Display name is meant to be user-visible and user-modifiable, it's not suitable for using as a login name. We store default_credentials_username for that purpose instead.
-
John Brooks authored
libsoup would escape parameters too much, resulting in authentication failures with some recent server-side changes by Facebook. The response string is simple to build and escaping is unnecessary for all feasible inputs.
-
- 10 Sep, 2013 1 commit
-
-
John Brooks authored
-
- 06 Sep, 2013 2 commits
-
-
John Brooks authored
This will be replaced by an API to trigger authentication failed notifications and have the user reauthenticate via the normal UI.
-
John Brooks authored
-
- 20 May, 2013 1 commit
-
-
John Brooks authored
This allows the use of, for example, password authentication on servers that also support oauth2, depending on which credential is actually configured.
-
- 20 Feb, 2013 1 commit
-
-
John Brooks authored
This is the last piece necessary for oauth support with our stack, so oauth is re-enabled as well.
-
- 19 Feb, 2013 1 commit
-
-
John Brooks authored
-
- 07 Dec, 2012 1 commit
-
-
John Brooks authored
-