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. Gitea
  3. Prevent external users joining gitea instance

Prevent external users joining gitea instance

Scheduled Pinned Locked Moved Gitea
13 Posts 5 Posters 1.6k Views 4 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.
  • fbartelsF Offline
    fbartelsF Offline
    fbartels
    App Dev
    wrote on last edited by fbartels
    #2

    You have this "sign in with oauth" button on your Gitea which, allows anybody that has an account on gitea.com to login and create an account on your instance.

    Edit: because of missing configuration that sign in button actually does not work (I just tested it now).

    If this instance is only supposed to be for you, you should also disabled registration in your gitea. the config option can be found in https://docs.gitea.com/next/administration/config-cheat-sheet#service-service and https://docs.cloudron.io/apps/gitea/ explains how to modify your gitea configuration.

    Edit2: I could confirm that with the gitea signup url (/user/sign_up) it is indeed possible to create an account on your system.

    1 Reply Last reply
    2
    • allanboweA Offline
      allanboweA Offline
      allanbowe
      wrote on last edited by
      #3

      Thankyou! This fixed it up.

      1 Reply Last reply
      1
      • fbartelsF Offline
        fbartelsF Offline
        fbartels
        App Dev
        wrote on last edited by
        #4

        @staff maybe it would be an idea to change the app that the default is a disabled registration. Sign in is the still possible with oauth.

        1 Reply Last reply
        2
        • SansGuidonS Offline
          SansGuidonS Offline
          SansGuidon
          wrote on last edited by SansGuidon
          #5

          I've also lost quite some time kicking accounts and repositories,
          in the end I've combined some of the options below (don't forget the [service] section marker and also restart after the changes !)

          [service]
          DISABLE_REGISTRATION = True
          REGISTER_MANUAL_CONFIRM = True
          EMAIL_DOMAIN_ALLOWLIST = XX_your_domain_here_XX,cloudron.local
          DEFAULT_USER_IS_RESTRICTED = True
          

          It's overkill if all are used at the same time, but depending on the needs and paranoia, it can be useful 🙂

          About me / Now

          1 Reply Last reply
          4
          • infogulchI infogulch referenced this topic
          • infogulchI Offline
            infogulchI Offline
            infogulch
            wrote last edited by infogulch
            #6

            +1 to "change the app so that the default is a disabled registration". I just had a big mess to clean up because of this. https://forum.cloudron.io/topic/14053/clean-up-external-users-that-have-accessed-gitea-instance

            At the very least these configs should be mentioned in the admin checklist.

            1 Reply Last reply
            2
            • SansGuidonS Offline
              SansGuidonS Offline
              SansGuidon
              wrote last edited by
              #7

              @girish could you please have a look at the suggestions here above about disabling registration by default to prevent spam? 🙏

              About me / Now

              1 Reply Last reply
              0
              • J Offline
                J Offline
                joseph
                Staff
                wrote last edited by
                #8

                Isn't it already false by default ? https://git.cloudron.io/packages/gitea-app/-/blob/master/app.ini.template?ref_type=heads#L78

                SansGuidonS 1 Reply Last reply
                0
                • J Offline
                  J Offline
                  joseph
                  Staff
                  wrote last edited by joseph
                  #9

                  I checked in a new install and registration is disabled by default afaict .

                  1 Reply Last reply
                  0
                  • J joseph

                    Isn't it already false by default ? https://git.cloudron.io/packages/gitea-app/-/blob/master/app.ini.template?ref_type=heads#L78

                    SansGuidonS Offline
                    SansGuidonS Offline
                    SansGuidon
                    wrote last edited by
                    #10

                    @joseph said in Prevent external users joining gitea instance:

                    Isn't it already false by default ? https://git.cloudron.io/packages/gitea-app/-/blob/master/app.ini.template?ref_type=heads#L78

                    I believe the flag should be set to True not False to block spam

                    About me / Now

                    J 1 Reply Last reply
                    0
                    • SansGuidonS SansGuidon

                      @joseph said in Prevent external users joining gitea instance:

                      Isn't it already false by default ? https://git.cloudron.io/packages/gitea-app/-/blob/master/app.ini.template?ref_type=heads#L78

                      I believe the flag should be set to True not False to block spam

                      J Offline
                      J Offline
                      joseph
                      Staff
                      wrote last edited by
                      #11

                      @SansGuidon of course 😄 Not sure what i was thinking... Which makes me wonder how come I didn't find any registration button .

                      1 Reply Last reply
                      2
                      • infogulchI Offline
                        infogulchI Offline
                        infogulch
                        wrote last edited by
                        #12

                        Maybe because the next line is SHOW_REGISTRATION_BUTTON = false. Not sure what this combination of features does, maybe it hides the register button but allows direct POST requests to the endpoint anyway?

                        1 Reply Last reply
                        1
                        • infogulchI Offline
                          infogulchI Offline
                          infogulch
                          wrote last edited by
                          #13
                          This post is deleted!
                          1 Reply Last reply
                          0
                          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