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. Stirling-PDF
  3. Getting cloudron auth back

Getting cloudron auth back

Scheduled Pinned Locked Moved Stirling-PDF
8 Posts 5 Posters 1.5k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic was forked from Stirling-PDF - Package Updates girish
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    jayonrails
    translator
    wrote on last edited by
    #1

    Any chances on getting the Cloudron authentication back to Stirling PDF?

    1 Reply Last reply
    0
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      Not really , why do you need it though?

      1 Reply Last reply
      0
      • U Offline
        U Offline
        uwcrbc
        wrote on last edited by
        #3

        I have not played much with the newer package version from my current understanding:

        • The authentication from the old package is app proxy based, allowing a user to use his/her/their cloudron's credential.
        • The authentication of the new package is a completely separated Stirling pdf authentication model (no LDAP/OIDC)

        This means users have yet to deal with a new username/password combo.
        It also means that admins have to deal with the whole setup/password reset work overhead.
        Also, no 2FA.

        Yet I understand that this is the direction Stirling-PDF is going to. Maybe OIDC is planned down the line.

        I also know of the enablelogin option which appeared in the latest release. However this simply opens the app instance to the public and does not bring back the Cloudron app proxy authentication (unless I overlooked something and their is a way to do this??).

        All in all, this isn't a complain - I understand the predicament of Cloudron package following the app development. This is intended as an explanation about while one would need it.

        girishG 1 Reply Last reply
        1
        • U uwcrbc

          I have not played much with the newer package version from my current understanding:

          • The authentication from the old package is app proxy based, allowing a user to use his/her/their cloudron's credential.
          • The authentication of the new package is a completely separated Stirling pdf authentication model (no LDAP/OIDC)

          This means users have yet to deal with a new username/password combo.
          It also means that admins have to deal with the whole setup/password reset work overhead.
          Also, no 2FA.

          Yet I understand that this is the direction Stirling-PDF is going to. Maybe OIDC is planned down the line.

          I also know of the enablelogin option which appeared in the latest release. However this simply opens the app instance to the public and does not bring back the Cloudron app proxy authentication (unless I overlooked something and their is a way to do this??).

          All in all, this isn't a complain - I understand the predicament of Cloudron package following the app development. This is intended as an explanation about while one would need it.

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #4

          @uwcrbc great explainer 🙂 that's exactly the situation we find ourselves in. We added cloudron auth initially because upstream had no auth. But now it has auth, so it's always better to use upstream auth. I hope they implement LDAP or OIDC. Stirling is also a relatively new app still very much in development, so one has to give it time.

          Another aspect was that Stirling has an API. If we use cloudron auth, this prevents API use. Many people already mentioned that the API is one of the main use cases for Stirling.

          U 1 Reply Last reply
          2
          • girishG girish

            @uwcrbc great explainer 🙂 that's exactly the situation we find ourselves in. We added cloudron auth initially because upstream had no auth. But now it has auth, so it's always better to use upstream auth. I hope they implement LDAP or OIDC. Stirling is also a relatively new app still very much in development, so one has to give it time.

            Another aspect was that Stirling has an API. If we use cloudron auth, this prevents API use. Many people already mentioned that the API is one of the main use cases for Stirling.

            U Offline
            U Offline
            uwcrbc
            wrote on last edited by
            #5

            @girish Thanks for this.
            I did not know about the API limitation but this seems logical.

            Let's hope indeed that LDAP/OIDC is on there roadmap.
            According to their Github, features request seems to be on their Discord. Possibly their roadmap too.
            Yet Discord is a bridge too far for me. Maybe a fellow "Cloudronite" with a discord account has already checked this though?

            Thanks again,

            1 Reply Last reply
            1
            • andreasduerenA Offline
              andreasduerenA Offline
              andreasdueren
              wrote on last edited by
              #6

              Piggibacking on this threat: why is security: enableLogin: true # set to 'true' to enable login overwritten on restart? I'd like to open up my instance.

              girishG 1 Reply Last reply
              1
              • andreasduerenA andreasdueren

                Piggibacking on this threat: why is security: enableLogin: true # set to 'true' to enable login overwritten on restart? I'd like to open up my instance.

                girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #7

                @andreasdueren this was a bug in the package, can you update and try again? It shouldn't get reset anymore.

                1 Reply Last reply
                1
                • F Offline
                  F Offline
                  froodle
                  wrote on last edited by
                  #8

                  LDAP is in roadmap! Although no ETA
                  Also most feature requests are done by GitHub issue tickets not discord otherwise it's hard to track over time

                  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