Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(conversations): fix password enforcement logic error #13944

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

miaulalala
Copy link
Contributor

@miaulalala miaulalala commented Dec 5, 2024

☑️ Resolves

Passwords should be settable on public rooms no matter if the force_passwords options is set. Only check if a password is set if the option is set to true and the room is public, but still let public rooms set a password independent from the option.

🛠️ API Checklist

🚧 Tasks

  • ...

🏁 Checklist

  • ⛑️ Tests (unit and/or integration) are included or not possible
  • 📘 API documentation in docs/ has been updated or is not required
  • 🔖 Capability is added or not needed

@miaulalala miaulalala added 3. to review bug feature: api 🛠️ OCS API for conversations, chats and participants feature: conversations 👥 labels Dec 5, 2024
@miaulalala miaulalala added this to the 🖤 Next Major (31) milestone Dec 5, 2024
@miaulalala miaulalala self-assigned this Dec 5, 2024
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.

Could add an integration test?

lib/Service/RoomService.php Outdated Show resolved Hide resolved
@nickvergessen
Copy link
Member

/backport to stable30

@miaulalala miaulalala force-pushed the fix/password-enforcement-logic-error branch from cb81d8d to ac0bfcc Compare December 11, 2024 13:54
@miaulalala miaulalala enabled auto-merge December 11, 2024 13:54
@@ -111,3 +111,9 @@ Feature: chat-2/public
And user "participant1" renames room "public room" to "A name with 260 chars 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12345678" with 400 (v4)
# 255 chars
And user "participant1" renames room "public room" to "Another name with 255 chars 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 1234567" with 200 (v4)

Scenario: Create public room with a password
When user "participant1" creates room "public room" with 201 (v4)
Copy link
Member

Choose a reason for hiding this comment

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

also add one where you set the config to "required" and try to create one without sending a password and expect 400?

@miaulalala miaulalala merged commit 9ce820b into main Dec 11, 2024
74 checks passed
@miaulalala miaulalala deleted the fix/password-enforcement-logic-error branch December 11, 2024 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review bug feature: api 🛠️ OCS API for conversations, chats and participants feature: conversations 👥
Projects
Status: ☑️ Done
Development

Successfully merging this pull request may close these issues.

3 participants