Skip to content

feat(api): Add context parameter to generate and validate endpoints#896

Merged
susnux merged 2 commits intomasterfrom
fix/share-password-policy-generation
Feb 15, 2026
Merged

feat(api): Add context parameter to generate and validate endpoints#896
susnux merged 2 commits intomasterfrom
fix/share-password-policy-generation

Conversation

@nfebe
Copy link
Contributor

@nfebe nfebe commented Feb 10, 2026

The API endpoints now accept a 'context' parameter to specify which password policy set to use (account or sharing). This allows the files_sharing app to generate and validate passwords against the share-specific password policy instead of the default account policy.

Fixes: #870

The API endpoints now accept a 'context' parameter to specify which
password policy set to use (account or sharing). This allows the
files_sharing app to generate and validate passwords against the
share-specific password policy instead of the default account policy.

Fixes: #870
Signed-off-by: nfebe <fenn25.fn@gmail.com>
@nfebe nfebe force-pushed the fix/share-password-policy-generation branch from c464284 to d4a04f3 Compare February 10, 2026 13:35
@nfebe nfebe requested review from nickvergessen and susnux and removed request for susnux February 10, 2026 13:36
Copy link
Contributor

@susnux susnux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just the version - otherwise fine!

Copy link
Member

@nickvergessen nickvergessen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was about to send the same PR as Talk iOS implemented it and we noticed they can't specify the context.
So backporting would be appreciated

Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
@susnux susnux merged commit ced666d into master Feb 15, 2026
48 checks passed
@susnux susnux deleted the fix/share-password-policy-generation branch February 15, 2026 16:27
@susnux
Copy link
Contributor

susnux commented Feb 15, 2026

/backport d4a04f3 to stable33

@backportbot
Copy link

backportbot bot commented Feb 15, 2026

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/896/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick d4a04f3c

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/896/stable33

Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/896/stable33."} - https://docs.github.com/rest/pulls/pulls#create-a-pull-request


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@susnux
Copy link
Contributor

susnux commented Feb 15, 2026

/backport d4a04f3 to stable32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Randomly generated password not complying with external sharing password policy

3 participants