Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. MiroTalk
  3. Use Cloudron Logins for host protected settings

Use Cloudron Logins for host protected settings

Scheduled Pinned Locked Moved Solved MiroTalk
mirotalk
47 Posts 9 Posters 4.0k Views 9 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C cvachery

    I did the same but ticked Allow all users from this Cloudron
    Thing is @jdaviescoates by default anyone can create/join a room. But I want to restrict room creation to logged in users and anyone can join with the link.
    And when activating those parameters is when problems arise.

    jdaviescoatesJ Offline
    jdaviescoatesJ Offline
    jdaviescoates
    wrote on last edited by
    #30

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

    Thing is @jdaviescoates by default anyone can create/join a room. But I want to restrict room creation to logged in users and anyone can join with the link.

    Ah, right. That ought to be default when choosing Cloudron user management, but I guess it isn't.

    I use Cloudron with Gandi & Hetzner

    1 Reply Last reply
    0
    • MiroTalkM MiroTalk

      @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.

      C Offline
      C Offline
      cvachery
      wrote on last edited by
      #31

      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 URL

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

      @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.

      MiroTalkM 1 Reply Last reply
      1
      • C cvachery

        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 URL

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

        @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.

        MiroTalkM Offline
        MiroTalkM Offline
        MiroTalk
        wrote on last edited by
        #32

        @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.

        N 1 Reply Last reply
        3
        • nebulonN Offline
          nebulonN Offline
          nebulon
          Staff
          wrote on last edited by
          #33

          Both packages are updated also now.

          1 Reply Last reply
          1
          • MiroTalkM MiroTalk

            @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.

            N Offline
            N Offline
            Neiluj
            wrote on last edited by Neiluj
            #34

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

            @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.

            Yeah I am still having issue with this / cannot figure out the correct settings to prevent anonymous user room creation.

            Basically, I am trying to limit room creation to registered Cloudron User, but still keep the possibility for anonymous users to join a room once created.

            At the moment, my MiroTalk SFU app has its cloudron setting access control set to "Only allow the following users and groups".

            I do have a custom config.js with the following:

                host: {
                    /*
                        Host Protection (default: false)
                        To enhance host security, enable host protection - user auth and provide valid
                        usernames and passwords in the users array.
                    */
                    protected: true,
                    user_auth: false,
                    users: [
                        /*
                        {
                            username: 'username',
                            password: 'password',
                        },
                        {
                            username: 'username2',
                            password: 'password2',
                        },
                        ...
                        */
                    ]
                },
            

            Yet room creation is still allowed for anonymous users.

            I could set user_auth to true and provider "provide valid usernames and passwords in the users array." as mentioned in the config.js comment, but my understanding is that this will void/conflict with the cloudron OIDC integration.

            Of course, I am likely missing something so I am wondering if anyone got this working properly and if/when so, what are the proper settings for preventing room creation by anonymous users.

            Many thanks,

            MiroTalkM 1 Reply Last reply
            0
            • N Neiluj

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

              @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.

              Yeah I am still having issue with this / cannot figure out the correct settings to prevent anonymous user room creation.

              Basically, I am trying to limit room creation to registered Cloudron User, but still keep the possibility for anonymous users to join a room once created.

              At the moment, my MiroTalk SFU app has its cloudron setting access control set to "Only allow the following users and groups".

              I do have a custom config.js with the following:

                  host: {
                      /*
                          Host Protection (default: false)
                          To enhance host security, enable host protection - user auth and provide valid
                          usernames and passwords in the users array.
                      */
                      protected: true,
                      user_auth: false,
                      users: [
                          /*
                          {
                              username: 'username',
                              password: 'password',
                          },
                          {
                              username: 'username2',
                              password: 'password2',
                          },
                          ...
                          */
                      ]
                  },
              

              Yet room creation is still allowed for anonymous users.

              I could set user_auth to true and provider "provide valid usernames and passwords in the users array." as mentioned in the config.js comment, but my understanding is that this will void/conflict with the cloudron OIDC integration.

              Of course, I am likely missing something so I am wondering if anyone got this working properly and if/when so, what are the proper settings for preventing room creation by anonymous users.

              Many thanks,

              MiroTalkM Offline
              MiroTalkM Offline
              MiroTalk
              wrote on last edited by
              #35

              @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!

              1 Reply Last reply
              2
              • nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by
                #36

                @Neiluj I just tried this here also with MiroTalk SFU and without changing the app configs manually, just install the app with Cloudron usermanagement enabled and then only authenticated users can create meetings, while everyone can join them with the share link.

                mdc773M 1 Reply Last reply
                2
                • nebulonN nebulon

                  @Neiluj I just tried this here also with MiroTalk SFU and without changing the app configs manually, just install the app with Cloudron usermanagement enabled and then only authenticated users can create meetings, while everyone can join them with the share link.

                  mdc773M Offline
                  mdc773M Offline
                  mdc773
                  wrote on last edited by
                  #37

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

                  @Neiluj I just tried this here also with MiroTalk SFU and without changing the app configs manually, just install the app with Cloudron usermanagement enabled and then only authenticated users can create meetings, while everyone can join them with the share link.

                  cant login when i follow your direction

                  1 Reply Last reply
                  0
                  • nebulonN Offline
                    nebulonN Offline
                    nebulon
                    Staff
                    wrote on last edited by
                    #38

                    was the app installed with Cloudron usermanagement? If so do you see an error somewhere?

                    mdc773M 1 Reply Last reply
                    0
                    • nebulonN nebulon

                      was the app installed with Cloudron usermanagement? If so do you see an error somewhere?

                      mdc773M Offline
                      mdc773M Offline
                      mdc773
                      wrote on last edited by
                      #39

                      @nebulon Yes cloudron user management was selected. Wired now when i vist a room and does not prompt the user auth just lunches the room: /

                      1 Reply Last reply
                      0
                      • nebulonN Offline
                        nebulonN Offline
                        nebulon
                        Staff
                        wrote on last edited by
                        #40

                        I think a direct link is like a public link share unless the room is protected, so that might be expected on how the app is currently written

                        mdc773M 1 Reply Last reply
                        0
                        • nebulonN nebulon

                          I think a direct link is like a public link share unless the room is protected, so that might be expected on how the app is currently written

                          mdc773M Offline
                          mdc773M Offline
                          mdc773
                          wrote on last edited by
                          #41

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

                          I think a direct link is like a public link share unless the room is protected, so that might be expected on how the app is currently written

                          even if i enable protection still cant use couldron account

                          jdaviescoatesJ 1 Reply Last reply
                          0
                          • mdc773M mdc773

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

                            I think a direct link is like a public link share unless the room is protected, so that might be expected on how the app is currently written

                            even if i enable protection still cant use couldron account

                            jdaviescoatesJ Offline
                            jdaviescoatesJ Offline
                            jdaviescoates
                            wrote on last edited by jdaviescoates
                            #42

                            @mdc773 I think perhaps you're missing something here.

                            If you're already logged into your Cloudron dashboard in the same browser you visit your MiroTalk app URL, it doesn't prompt for auth - it just magically checks if you're logged in and if you are just automatically logs you in.

                            But if you visit the same URL in a private tab you should indeed get prompted to login to Cloudron.

                            At least that's what happens for me.

                            I am logged into my Cloudron dashboard, so when I visit my MiroTalk URL I arrive here:

                            3c0c3711-4567-405e-83ab-b851f31a41b6-image.png

                            But if I visit the same URL in a private tab I get this:

                            4ad9ae9f-beae-4c24-92b5-bf532a8cf8d5-image.png

                            I also just double checked and if you try to visit a join URL of a meeting after the logged in person has left the meeting, it no longer works and you are presented with the login screen again.

                            I use Cloudron with Gandi & Hetzner

                            mdc773M 1 Reply Last reply
                            3
                            • jdaviescoatesJ jdaviescoates

                              @mdc773 I think perhaps you're missing something here.

                              If you're already logged into your Cloudron dashboard in the same browser you visit your MiroTalk app URL, it doesn't prompt for auth - it just magically checks if you're logged in and if you are just automatically logs you in.

                              But if you visit the same URL in a private tab you should indeed get prompted to login to Cloudron.

                              At least that's what happens for me.

                              I am logged into my Cloudron dashboard, so when I visit my MiroTalk URL I arrive here:

                              3c0c3711-4567-405e-83ab-b851f31a41b6-image.png

                              But if I visit the same URL in a private tab I get this:

                              4ad9ae9f-beae-4c24-92b5-bf532a8cf8d5-image.png

                              I also just double checked and if you try to visit a join URL of a meeting after the logged in person has left the meeting, it no longer works and you are presented with the login screen again.

                              mdc773M Offline
                              mdc773M Offline
                              mdc773
                              wrote on last edited by
                              #43

                              @jdaviescoates awesome i was wondering how i did not think of this

                              silly me

                              1 Reply Last reply
                              1
                              • nebulonN Offline
                                nebulonN Offline
                                nebulon
                                Staff
                                wrote on last edited by
                                #44

                                @jdaviescoates good guess to resolve this quicker!

                                1 Reply Last reply
                                2
                                • nebulonN nebulon has marked this topic as solved on
                                • A Offline
                                  A Offline
                                  admeister
                                  wrote last edited by
                                  #45

                                  Hi there,

                                  re: Mirotalk SFU 1.9.77

                                  I'm trying to configure Mirotalk SFU to only allow logged in Cloudron users to join a room.

                                  If I'm reading this thread correctly, I don't need to include any OIDC settings in the env file anymore - so this is what my env file looks like, attached.

                                  As the host, Mirotalk now (incorrectly) says that I am not logged in myself (even though I launched MiroTalk from my Cloudron admin dashboard), and then it asks me to login with the MiroTalk interface itself (and not the Cloudron login). When I attempt to use my Cloudron login details it says I have invalid credentials.

                                  So do I actually need to configure all the OIDC settings in the env file? If so, can I pls get some guidance on how to arrive at the exact settings needed?

                                  Thank you! 🙂
                                  Ads

                                  SCR-20251006-nglp.png

                                  MiroTalkM 1 Reply Last reply
                                  1
                                  • A admeister

                                    Hi there,

                                    re: Mirotalk SFU 1.9.77

                                    I'm trying to configure Mirotalk SFU to only allow logged in Cloudron users to join a room.

                                    If I'm reading this thread correctly, I don't need to include any OIDC settings in the env file anymore - so this is what my env file looks like, attached.

                                    As the host, Mirotalk now (incorrectly) says that I am not logged in myself (even though I launched MiroTalk from my Cloudron admin dashboard), and then it asks me to login with the MiroTalk interface itself (and not the Cloudron login). When I attempt to use my Cloudron login details it says I have invalid credentials.

                                    So do I actually need to configure all the OIDC settings in the env file? If so, can I pls get some guidance on how to arrive at the exact settings needed?

                                    Thank you! 🙂
                                    Ads

                                    SCR-20251006-nglp.png

                                    MiroTalkM Offline
                                    MiroTalkM Offline
                                    MiroTalk
                                    wrote last edited by MiroTalk
                                    #46

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

                                    I'm trying to configure Mirotalk SFU to only allow logged in Cloudron users to join a room.

                                    Simply remove all the old or unnecessary entries from your env file:

                                    del.png

                                    Note: The parameter ALLOW_ROOM_CREATION_WITHOUT_HOST is not related to MiroTalk SFU.

                                    To explicitly configure MiroTalk with Cloudron OIDC Authentication (this is also the default behavior if not explicitly set), use the following environment variables:

                                    OIDC_ENABLED=true
                                    OIDC_ALLOW_ROOMS_CREATION_FOR_AUTH_USERS=true
                                    
                                    • OIDC_ENABLED=true — Enables OIDC authentication.
                                    • OIDC_ALLOW_ROOMS_CREATION_FOR_AUTH_USERS=true — Allows all authenticated users via OIDC to create their own rooms.

                                    If you do not want to use OIDC authentication but still want to define your own user logins, you can disable OIDC and enable MiroTalk SFU internal Host Protection Mode:

                                    # Disable Cloudron OIDC
                                    OIDC_ENABLED=false
                                    
                                    # Host protection
                                    HOST_PROTECTED=true
                                    HOST_USER_AUTH=false
                                    
                                    # Define host users in the format:
                                    # username:password:displayName:allowedRooms (comma-separated)
                                    HOST_USERS="user1:pass1:user-1:*|user2@mail.com:pass2:user two:*|user3:pass3:user name:*"
                                    
                                    • HOST_PROTECTED=true — Enables Host Protection mode.
                                    • HOST_USER_AUTH=false — Disables additional user authentication beyond host users.
                                    • HOST_USERS — List of host users, with * allowing access to all rooms or specific room names separated by commas.

                                    ⚠️ After making changes, restart your MiroTalk instance for them to take effect.


                                    For a complete environment configuration, check the .env.template file:
                                    Full env example

                                    The environment variables are loaded in config.js and serve both as runtime configuration and documentation for additional features:
                                    Full config.js example

                                    1 Reply Last reply
                                    4
                                    • A Offline
                                      A Offline
                                      admeister
                                      wrote last edited by admeister
                                      #47

                                      Thank you everyone for your responses.

                                      I'm trying to configure Mirotalk SFU to only allow logged in Cloudron users to join a room.

                                      Realised that the solution was far simpler than I thought - I just needed to add a single line to the .env file:

                                      OIDC_AUTH_REQUIRED=true

                                      Thank you deeply to everyone working on Cloudron and all associated apps... I'm in awe of this community!

                                      Ads

                                      1 Reply Last reply
                                      3
                                      Reply
                                      • Reply as topic
                                      Log in to reply
                                      • Oldest to Newest
                                      • Newest to Oldest
                                      • Most Votes


                                      • Login

                                      • Don't have an account? Register

                                      • Login or register to search.
                                      • First post
                                        Last post
                                      0
                                      • Categories
                                      • Recent
                                      • Tags
                                      • Popular
                                      • Bookmarks
                                      • Search