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
  • 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. Uptime Kuma
  3. HTTP Authentication for Kuma

HTTP Authentication for Kuma

Scheduled Pinned Locked Moved Uptime Kuma
9 Posts 6 Posters 1.6k Views 6 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.
    • F Offline
      F Offline
      fiwand
      wrote on last edited by fiwand
      #1

      Kuma only supports a single admin user account, but provides two features for team/public access:

      • the ability to create a public dashboard
      • the option to completely disable Kuma's authentication

      We'd like to use the public dashboard feature as an internal dashboard, but cannot currently do so because our Cloudron instance is public-facing.

      Is there a way to add an optional HTTP authentication layer to the Kuma Cloudron app? A single set of credentials would be perfectly fine for our use case, but we're also OK if other authentication requirements, like being a cloudron user, would make an integration easier or more versatile. We also don't need the authentication to only target specific paths.

      Thanks!

      robiR 1 Reply Last reply
      1
      • F fiwand

        Kuma only supports a single admin user account, but provides two features for team/public access:

        • the ability to create a public dashboard
        • the option to completely disable Kuma's authentication

        We'd like to use the public dashboard feature as an internal dashboard, but cannot currently do so because our Cloudron instance is public-facing.

        Is there a way to add an optional HTTP authentication layer to the Kuma Cloudron app? A single set of credentials would be perfectly fine for our use case, but we're also OK if other authentication requirements, like being a cloudron user, would make an integration easier or more versatile. We also don't need the authentication to only target specific paths.

        Thanks!

        robiR Offline
        robiR Offline
        robi
        wrote on last edited by
        #2

        @fiwand Check to see if Kuma uses Apache and manually modify the .htaccess file.

        Conscious tech

        fbartelsF 1 Reply Last reply
        0
        • robiR robi

          @fiwand Check to see if Kuma uses Apache and manually modify the .htaccess file.

          fbartelsF Offline
          fbartelsF Offline
          fbartels
          App Dev
          wrote on last edited by
          #3

          @robi it doen't btw https://git.cloudron.io/cloudron/uptime-kuma-app/-/blob/master/start.sh

          Maybe one can mod the app to use https://docs.cloudron.io/packaging/addons/#proxyauth.

          robiR 1 Reply Last reply
          2
          • fbartelsF fbartels

            @robi it doen't btw https://git.cloudron.io/cloudron/uptime-kuma-app/-/blob/master/start.sh

            Maybe one can mod the app to use https://docs.cloudron.io/packaging/addons/#proxyauth.

            robiR Offline
            robiR Offline
            robi
            wrote on last edited by
            #4

            @fbartels or a separate custom nginx config for the kuma subdomain that does it in addition to the default route.

            Conscious tech

            1 Reply Last reply
            0
            • W Offline
              W Offline
              wind.gmbh
              wrote on last edited by
              #5

              This is probably related to a feature request I have made a couple of weeks ago:

              1 Reply Last reply
              1
              • girishG Do not disturb
                girishG Do not disturb
                girish
                Staff
                wrote on last edited by
                #6

                I think we have to implement some app level access level control as @wind-gmbh suggested.

                robiR 1 Reply Last reply
                2
                • girishG girish

                  I think we have to implement some app level access level control as @wind-gmbh suggested.

                  robiR Offline
                  robiR Offline
                  robi
                  wrote on last edited by
                  #7

                  @girish said in HTTP Authentication for Kuma:

                  I think we have to implement some app level access level control as @wind-gmbh suggested.

                  Agreed, a general Cloudron LDAP + unique pw for different occasions changeable in the UI, per app would be very useful.

                  Conscious tech

                  1 Reply Last reply
                  0
                  • matbrgzM Offline
                    matbrgzM Offline
                    matbrgz
                    wrote on last edited by
                    #8

                    Hey, take a look at https://github.com/louislam/uptime-kuma/issues/1756#issuecomment-1158597816 they use HTTP Authentication.

                    Currently, is there any solution for it?

                    girishG 1 Reply Last reply
                    0
                    • matbrgzM matbrgz

                      Hey, take a look at https://github.com/louislam/uptime-kuma/issues/1756#issuecomment-1158597816 they use HTTP Authentication.

                      Currently, is there any solution for it?

                      girishG Do not disturb
                      girishG Do not disturb
                      girish
                      Staff
                      wrote on last edited by
                      #9

                      @matbrgz I think that ends up protected all of uptime kuma and not just the status page . But of course, one can always tinker the configs in such a way that only specific pages are protected (one has to also investigate protecting API requests to the backend etc). I think this has to be implemented in uptime kuma itself to be fixed reliably.

                      1 Reply Last reply
                      1
                      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