Guest access still allowed & guidance on authentication via ICE

[Nablusi]

Hello,

I am integrating a Mumble server with my backend using the ICE API, and I am facing two issues related to authentication and access control.

1) Guest access issue

I have configured my Mumble server to disallow guests, however I am still able to connect as a guest user.

Current server behavior:

• When connecting as a guest, the server asks for the server password
• After entering the server password, the guest is allowed to connect and can see all channels

My understanding was that:

• allowunregistered=false should block all guest / unregistered users
• Only users registered via ICE should be able to connect

However, this does not seem to be enforced in my setup.
Could you please clarify:

• Under what conditions allowunregistered=false is enforced?
• Whether there are additional settings required when using ICE to fully block guest access?

---

2) Authentication using ICE (best practice)

I manage my own users in an external database and register them in Mumble using the ICE API (registerUser).

I would like to understand the recommended authentication flow when using ICE:

• How should authentication be enforced so that only ICE-registered users can connect?
• Is certificate-based authentication (certrequired=true) the correct and recommended approach?
• Are there any ICE hooks or callbacks intended for custom authentication logic?

My goal is to build a multi-tenant system where:

• Only backend-approved users can connect
• Guests and random usernames are completely blocked
• Access is controlled by ICE and ACLs

Any clarification, examples, or documentation references would be greatly appreciated.

[pepone]

Hi @Nablusi

You may want to ask this question in the Mumble project channels, where the developers and community are more familiar with these details.

These are not Ice APIs, they are Mumble Server APIs that use Ice for the implementation.