Skip to content

jitsi-server changes the default configuration to require user authentication #343

Description

@ThubLives

The Jitsi project provides packages that require no authentication, providing a frictionless user experience, but the droplet setup script changes the configuration to require authentication. I've been trying to figure out how to revert to the default configuration, but all the available documentation (including docs from Digital Ocean) assume the Jitsi project's default of no authentication as a starting point.

I suggest either leaving the defaults alone or providing documentation on how to revert the configuration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions