| Age | Commit message (Collapse) | Author |
|---|
|
|
|
It was deleting too many cookies.
That function is virtual in Qt5 and is used when adding cookie.
But some Shibboleth have several cookies with the same name, and we need to keep them.
Our implementaiton was meant to delete all the shiboleth cookies when we want to log out
|
|
|
|
This allows to handle the --trust option in owncloudcmd. In the
owncloudcmd subclass of the httpcredentials, we allow to manually trust
the ssl certificate through a command line switch.
|
|
#2211
|
|
Conflicts:
VERSION.cmake
|
|
It is not enough to only implement it for the QNAM returned
by the ShibbolethCredentials, because we sometimes need it
when we have no valid credentials set (and are using dummy
credentials in the course). The main use case is the
Webview opened by Shibboleth for FBA.
But as a side-effect, we can use it to handle auth requests
from the updater and other places.
|
|
Conflicts:
doc/ocdoc
|
|
When the url do not have a path (for example: "http://example.com" as
opposed to "http://example.com/"), its path is not a prefix of the
root path of the cookie (usually '/')
By adding the dav path, we make sure the URL has a path.
This made a bug when the owncloud url was just a domain name and did not
have a path
|
|
Conflicts:
VERSION.cmake
|
|
|
|
Conflicts:
src/mirall/folder.cpp
src/mirall/propagator_qnam.cpp
|
|
Conflicts:
VERSION.cmake
src/mirall/syncengine.cpp
src/mirall/syncengine.h
|
|
This was made automatically with
clang-modernize -override-macros -add-override
|
|
Fix #1915
|
|
But in case the user clicks cancel in the interactive dialog, invalidate
the credentials. Emit fechted() also in error case.
|
|
Earlier clients used QtKeychain without a QSettings object, which made
QtKeychain to write the password encrypted into a settings default
location, ie. the registry under windows.
If we can not find a password at the new location it is tried to read
the password from the old default location once. That makes people
happy in migration scenarios.
|
|
|
|
Conflicts:
VERSION.cmake
doc/building.rst
|
|
The mutex is not shared with any thread, so it is totaly useless.
Yes: there are possible races here. (with the account, but also with the
user and password)
|
|
Otherwise the user is asked twice for autentication on first sync.
Fixes https://github.com/owncloud/enterprise/issues/193
|
|
Conflicts:
VERSION.cmake
csync/src/csync_statedb.c
src/mirall/syncengine.cpp
src/mirall/syncfileitem.h
|
|
If we don't have the cookie in the keychain (e.g. the keychain is
unavailable) but there is still session cookie in the cookie jar,
showing the browser won't ask for authentication.
|
|
parseCookies did not work as expected. Now we just hard-set the
token credentials into the Cookie header for QNAM jobs.
This is the same behaviour as for neon jobs.
(cherry picked from commit 855a8c0a335f76b82b8e647a8c5a4ae692065d3b)
|
|
|
|
|
|
This is a relict from when the webview was reused.
It is now pointless, since it's now destruct-on-close.
|
|
Otherwise, QWebPage tries to delete its QNetworkReplies, which have
already been deleted by the QNAM destruction, who is their parent.
Fixes #1840
|
|
This is for server file backends that support sending a
direct URL.
|
|
|
|
This is designed as a passive popup notification so that it will
not surprise or annoy the users.
Fixes Enterprise issue #179
|
|
This should disconnect without loosing long lived cookie
|
|
|
|
When the windows is accepted, do not emit fetched which means the process is finished
one must first check the username is valid
|
|
window is open
This will cause the browser window to open again after it has been told to close
if a network job has run in the background while the browser window was visible.
Fixes #1814
|
|
|
|
|
|
|
|
|
|
The shibboleth implementation no longer maintains its own QNAM.
Instead, MirallAccessManager now holds a custom QNAM implementation
which saves cookies to a file on disk.
This patch also reduces some complexity wrt the browser window,
which used to be deleted via a roundtrip to its callee, which
is not longer required.
Fixes #1764 and Enterprise bug #165
Going forward, AbstractCredentials::getQNAM() could maybe removed entirely.
|
|
There is a HACK from commit fa0a2764a40d5955f1d3426481f998a370223290
Which save the http user as a user for all credidentials, but that
cannot work with shibboleth
Fixes https://github.com/owncloud/enterprise/issues/175
|
|
This was required so the compiler sees the declaration of
CredentialsFactory::create which should be exported
|
|
|
|
|
|
Not all the class are exported currently, only the one that seems to be used
by the command line tools
|
|
Copy the code from HTTPCredidentials
|
|
|
|
This allows to reuse the Job
|
|
..depending on Qt version
|
|
And a typo
|
