Cloudron Forum

@mdc773 said in when creating room no auth prompt:

all URLs should be protected not just the main root

In the OIDC settings, there is a parameter to make it possible

oidc: {
    config: {
        authRequired: true, // Set to true if authentication is required for all routes
    }
}

@jdaviescoates said in when creating room no auth prompt:

I'm not certain, but I think that license is probably mostly about the support you get from @MiroTalk

With the purchase of a license or for those who support the project in some way, my Direct support is included for any questions or concerns regarding MiroTalk. However, if your intention is to rebrand it by changing the logo, name, description, etc., a Regular License is required for personal, non-commercial projects. For commercial purposes or if you intend to charge end users, the Extended License is necessary.

Note: No monthly subscriptions are required; it's a one-time fee.

For more details about MiroTalk's licensing options, please visit: https://docs.mirotalk.com/license/licensing-options/

Thank you, and I take this opportunity to wish everyone a Happy 2025!

@jdaviescoates said in when creating room no auth prompt:

If I just go to https://mirotalk.ud.coop/ in a private browser window I get prompted to login, but if I go to https://mirotalk.ud.coop/wherever I don't

Should be fixed in the latest MiroTalk SFU release (v1.6.69).

@robi said in reconnecting to the meeting randomly:

grab some logs before you tag the dev?

I agree. If anyone believe something is not working as expected, please follow this template to report it to us.

Thank you for your collaboration.

@mdc773 said in reconnecting to the meeting randomly:

myself and others in the community sometimes get reconnected to the room

The cause could be:

1. Network Instability: Temporary internet disruptions, such as mobile devices switching between 3G and 4G, or high latency, may lead to participants reconnecting.
2. Server Restarts: If the server is restarted, for instance, after updates, participants may reconnect when the MiroTalk instance becomes available again.
3. WebRTC Behavior: WebRTC may renegotiate connections under certain conditions, which can appear as reconnections.

@mdc773 said in redirects:

@MiroTalk talk you so much sir

You're welcome, and enjoy your video conferences!

I’d also like to take this opportunity to wish everyone happy holidays and a happy New Year. See you next year!

Users can now join MiroTalk SFU (v1.6.52) and MiroTalk P2P (v1.4.12) rooms by visiting a simplified URL, such as meet.mysite/allwelcome, which will automatically redirect them to meet.mysite/join?room=allwelcome.

The Docker images will be updated and available in about an hour.

@jdaviescoates said in redirects:

What @mdc773 wants to be able to is to enable their users to just be able to type

https://sfu.mirotalk.com/allwelcome into their browser bar

And for the that to automatically redirect to https://sfu.mirotalk.com/join?room=allwelcome

Now I get it, I will make it possible in the next release!

@mdc773 said in redirects:

like meet.mysite/join?room=allwelcome

You can easily join a room by using this link with the query parameters:

https://sfu.mirotalk.com/join?room=allwelcome

For more ways to customize your room join process with different options, check out the full guide here: MiroTalk SFU Join Room Documentation.

@Neiluj If you have OIDC enabled, you can safely remove the entire host: { ... } section from your configuration. Simply rely on OIDC for authentication, and let me know if everything works as expected. Thank you!

@Joseph Thank you!

When the broadcaster leaves or a viewer disconnects, the viewer will be redirected to a new page.

@luckow said in MiroTalk Bro flavor: “home page link" (viewer perspective):

Have you seen anything that allows you to configure the URL of the home page? The moment a viewer clicks “Exit”, they are redirected to the Cloudron OIDC (login) form. Perhaps there is a more “elegant” way to redirect users.

The improvements are now live in MiroTalk BRO v1.0.66. For reference, please check the details here: MiroTalk BRO v1.0.66 Improvements.

@cvachery said in Use Cloudron Logins for host protected settings:

Thanks to @MiroTalk in the latest version it works and the config is nearly perfect
Only issue is still one identified erlier that anonymous users can create room if they go to the specific

Should be fixed in both MiroTalk P2P v.1.3.79 & MiroTalk SFU v.1.5.80. Cheers.

Hi everyone,

Are we still encountering the same popup message as before, or is this a new one (see attached image)?

If it’s this new one, did you notice any further issues after the popup appeared?

If it’s not, has anyone been able to consistently reproduce the original issue? If so, could you please share the exact steps to replicate it?

Thanks!

Should be fixed in MiroTalk SFU v.1.5.72. Cheers.

Hi @girish,
The ServerAway event occurs when the client socket disconnects from the MiroTalk SFU instance. This typically happens when a new release is deployed, necessitating a MiroTalk SFU restart to apply changes. As soon as the MiroTalk SFU comes back on (usually within a few seconds), all clients should automatically reconnect to the MiroTalk SFU again. Cheers.

@avatar1024 said in Use Cloudron Logins for host protected settings:

Otherwise, while guest cannot enter the app base domain without a login, they can still create rooms freely by creating a url: mirotalkappprefix.mydomain.com/join/roomname

@MiroTalk is that behaviour intended?

Not a behaviour intended! I'm considering a refinement where guests are only allowed to join specified rooms that have already been created by authenticated users. This approach might offer better control and security. Will be released in the next version.

@cvachery said in Use Cloudron Logins for host protected settings:

@Mirotalk did the update that was deployed to cloudron include the openid logins?

The OIDC (OpenID Connect) option is available in both MiroTalk P2P v.1.3.29 And MiroTalk SFU v.1.4.32.

It works like this:

1. Authentication Prompt: When someone wants to access restricted features on MiroTalk, they're asked to log in using a service like Auth0 or Other providers. This sends them to Auth0's login page to prove they're who they say they are.

2. Room Creation and Sharing: After logging in successfully, users can create and share rooms with others. This lets them collaborate easily within MiroTalk.

3. Guest Access Control: Guests (people who aren't logged in) can't access certain parts of MiroTalk, like the landing page or new room creation. They can only join rooms shared with them by someone who's logged in. This ensures that only verified users can use all of MiroTalk's features, keeping things safe and private.

How Does OIDC Fit In?

Now, instead of the old way where MiroTalk checked a config file or called an API to see if a user was valid, we can use OIDC for authentication. Here's how:

1. Full Authentication: If authRequired is set to true, everything in MiroTalk requires logging in. No login, no access.

2. Optional Authentication: With this setup, certain parts of MiroTalk might need authentication while others don't. Enabling OIDC with host_protection means that authenticated users can access the platform, while Guests can join room, like the old logic but in conjuction with OIDC.

3. No Authentication: In some cases, you might want MiroTalk to be completely open, no login needed. This is good for things like public resources or demos.

4. OIDC disabled: When OIDC is disabled, the previous logic remains in place.

That's the gist of it! OIDC gives us more options for keeping MiroTalk secure and flexible for different situations. Furthermore, for those who opt out of OIDC usage, our existing security measures remain intact.

@nebulon We're working on integrating OpenID Connect, and you can expect it to roll out with our upcoming release.

@cvachery Regarding room security, you have the option to set passwords for rooms directly from the Settings menu under Room/Lock Room.