| Age | Commit message (Collapse) | Author |
|---|
|
We're not interested in any found element in these cases, just to check
that none of the elements matches.
Signed-off-by: Harald Eilertsen <haraldei@anduin.net>
|
|
Signed-off-by: Harald Eilertsen <haraldei@anduin.net>
|
|
Signed-off-by: Harald Eilertsen <haraldei@anduin.net>
|
|
Signed-off-by: Kevin Ottens <kevin.ottens@nextcloud.com>
|
|
- When the the users logs because of 401 or 403 errors, it checks if the
server requested the remote wipe. If yes, locally deletes account and folders
connected to the account and notify the server. If no, proceeds to ask the
user to login again.
- The app password is restored in the keychain.
- WIP: The change also includes a test class for RemoteWipe.
Signed-off-by: Camila San <hello@camila.codes>
|
|
Instead of immediately popping up the mnemonic dialogue,
only show a notification bar on the account setup page.
For the cases where the user does not want to use E2E,
this is significantly less intrusive than the old approach.
|
|
Reported at Transifex.
Signed-off-by: Mark Ziegler <mark.ziegler@rakekniven.de>
|
|
Signed-off-by: Mark Ziegler <mark.ziegler@rakekniven.de>
|
|
This moves all the basic http auth over to the webflow mechanism.
This thus also makes sure that if the password changes a webflow page
pops up. And thus will directly move them over to apptokens then.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|
Fixed syntax error
Possible fix for issue #720
|
|
Fixed issue #720 by adding the isWrittable method
|
|
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
|
FIXES: #149
|
|
The libsync should not contain Qt Widget related code.
|
|
Thus making easier to exclude logging from kio, qt
and only enable "nextcloud.*"
|
|
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|
This is motivated by the fact that QMetaObject::noralizeSignature takes 7.35%
CPU of the LargeSyncBench. (Mostly from ABstractNetworkJob::setupConnections and
PropagateUploadFileV1::startNextChunk). It could be fixed by using normalized
signature in the connection statement, but i tought it was a good oportunity
to modernize the code.
This commit only contains calls that were automatically converted with clazy.
|
|
Now that csync builds as C++, this will avoid having to implement
functionalities needed by csync mandatorily in csync itself.
This library is built as part of libocsync and symbols exported
through it.
This requires a relicense of Utility as LGPL. All classes moved into
this library from src/libsync will need to be relicensed as well.
|
|
|
|
|
|
Use qCInfo for anything that has general value for support and
development. Use qCWarning for any recoverable error and qCCritical
for anything that could result in data loss or would identify a serious
issue with the code.
Issue #5647
|
|
This gives more insight about the logs and allow setting fine-tuned
logging rules. The categories are set to only output Info by default
so this allows us to provide more concise logging while keeping the
ability to extract more information for a specific category when
developping or debugging customer issues.
Issue #5647
|
|
Previously, we'd try migrating from legacy settings if reading
the settings failed with an error. Now, we try again after a
couple of seconds and eventually give up.
|
|
The QSettings object was not deleted in every possible code paths
|
|
This is a follow up to #5469
|
|
There have been hard to track down bugs related to the wrong auth
type being used.
|
|
|
|
The re-enables the UI, uses Qt API for importing and
stores the certificate/key in the system keychain.
People who had set up client certs need to re-setup the account. This is ok
since it was an undocumented feature anyway.
|
|
License: Adjust license of GPLv2 source files to GPLv2+
|
|
There was little reason to keep them cluttering Account.
|
|
It was unused since early in the multi-account work:
a932eac832b442cca763197240f036905dd284da
|
|
See #5180
|
|
Some tests (such as FolderManTest) can polute the config file with invalid
accounts.
(That's because most of the code, (even in libsync) always instentiate a ConfigFile)
|
|
While loading the account, only override the server url if Theme::forceConfigAuthType
is set. This restore the behavior from the client 2.1 for theme that did not
use Theme::forceConfigAuthType.
Issue: owncloud/enterprise#1418
|
|
the theme specify it (#4591)
That way an upgrade of the client can actually change the URL
Issue https://github.com/owncloud/enterprise/issues/1113
https://github.com/owncloud/enterprise/issues/1126
In addition to restoring commit 7e5d89293d7bd52ac42d026d34a8154fbbdf33bb, this
add a way to override the auth type
|
|
* A tray message on every start up
* Red message in account settings
* Folders are paused when the server version switches to
an unsupported one
|
|
This will be useful if we ever want to store account-level gui state.
I built this originally because I thought a paused account would be
this kind of state.
|
|
config if the theme specify it"
The URL may change from shiboleth to normal authentication method.
Also some people were changing the config file manually to test stuff
Issue https://github.com/owncloud/enterprise/issues/1113
This reverts commit 7e5d89293d7bd52ac42d026d34a8154fbbdf33bb.
|
|
the theme specify it
That way an upgrade of the client can actually change the URL
Issue https://github.com/owncloud/enterprise/issues/1113
|
|
It uses the Account displayName to destinguish.
|
|
|
|
And also introduce a Accounts/version int at the same time. That
may make future account settings migrations easier to manage.
|
|
|
|
|
|
|
|
The proxyAuthenticationRequired() signal now goes to the
ProxyAuthHandler class. That class will try to read the proxy settings
from the keychain or ask the user about them.
We won't ask the user for credentials for explicitly configured proxies.
It also does not change how the credentials for explicitly configured
proxies are stored. (see #261)
|
|
|
|
It is only used by the GUI. Also return a unique_ptr to make the ownership clearer
|
|
|
|
|
