| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
The scope design requires scopes to be either not specified, or
specified explicitely. Therefore, when setting the
skip-password-validation scope for user authentication from mechanisms
like SAML, we also have to set the filesystem scope, otherwise they will
lack access to the filesystem.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\
| |
| | |
[27] feat: add option to disable scanner transactions
|
| |
| |
| |
| | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
| |
| |
| |
| | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ \
| | |
| | | |
[stable27] fix(ObjectStore): Fix regression when hostname is empty
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes #45637
The support for s3-accelerate added in #44496 introduced a regression in AWS S3 environments when `hostname` is blank (which is a valid configuration w/ AWS since the hostname gets auto-generated).
Signed-off-by: Josh <josh.t.richards@gmail.com>
|
|\ \ \
| | | |
| | | | |
[stable27] Use isRetryable to catch retryable exceptions
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Louis Chemineau <louis@chmn.me>
|
| |/ /
|/| |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- "password-unconfirmable" is the effective name for 30, but a draft
name was backported.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SSO backends like SAML and OIDC tried a trick to suppress password
confirmations as they are not possible by design. At least for SAML it was
not reliable when existing user backends where used as user repositories.
Now we are setting a special scope with the token, and also make sure that
the scope is taken over when tokens are regenerated.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \ |
|
| | |
| | |
| | | |
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
[skip ci]
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Anna Larch <anna@nextcloud.com>
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \ \ \
| | | | |
| | | | | |
[stable27] fix: Mark more configs as sensitive
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
| |_|_|/
|/| | |
| | | |
| | | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \ \ \
| |/ / /
|/| | | |
[stable27] perf(db): Sort data for IN before chunking
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
|
|\ \ \ \
| | | | |
| | | | | |
[stable27] Avoid updating the same oc_authtoken row twice
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Mimic behaviour from LDAP users and add a hard limit to 255 characters
Signed-off-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
Signed-off-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
|
|\ \ \ \ \
| | | | | |
| | | | | | |
[stable27] fix(session): Do not update authtoken last_check for passwordless
|
| | |_|_|/
| |/| | |
| | | | |
| | | | | |
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Sorting the events by the start date leads to more predictable results for the search API consumers.
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|\ \ \ \
| | | | |
| | | | | |
[stable27] Respect empty `expiryDate` value in server
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Verify that explicitly sending empty `expireDate` param to server overwrite default
and sets not expiry date, if non is enforced.
- Update tests to avoid converting empty string to date.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
If `expireDate` is an empty string and not `null` then the server should not set a default.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
|\ \ \ \
| | | | |
| | | | | |
[stable27] fix(memcache): remove double $$ to fix error
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
Extra Dollar Sign caused errors in Nextcloud. Removing the Dollar Sign Solved the Problem.
Signed-off-by: Velwark <levinfrerich9@gmail.com>
|
|/ / /
| | |
| | |
| | | |
Signed-off-by: Sam Bull <git@sambull.org>
|
| | |
| | |
| | | |
Signed-off-by: yemkareems <yemkareems@gmail.com>
|