<![CDATA[Getting cloudron auth back]]>Any chances on getting the Cloudron authentication back to Stirling PDF?

]]>https://forum.cloudron.io/topic/10497/getting-cloudron-auth-backRSS for NodeSat, 13 Jun 2026 15:07:38 GMTWed, 22 Nov 2023 01:47:58 GMT60<![CDATA[Reply to Getting cloudron auth back on Sat, 02 Dec 2023 09:14:52 GMT]]>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

]]>https://forum.cloudron.io/post/78621https://forum.cloudron.io/post/78621Sat, 02 Dec 2023 09:14:52 GMT<![CDATA[Reply to Getting cloudron auth back on Fri, 01 Dec 2023 09:50:13 GMT]]>@andreasdueren this was a bug in the package, can you update and try again? It shouldn't get reset anymore.

]]>https://forum.cloudron.io/post/78570https://forum.cloudron.io/post/78570Fri, 01 Dec 2023 09:50:13 GMT<![CDATA[Reply to Getting cloudron auth back on Fri, 01 Dec 2023 03:21:16 GMT]]>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.

]]>https://forum.cloudron.io/post/78559https://forum.cloudron.io/post/78559Fri, 01 Dec 2023 03:21:16 GMT<![CDATA[Reply to Getting cloudron auth back on Tue, 28 Nov 2023 10:54:07 GMT]]>@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,

]]>https://forum.cloudron.io/post/78343https://forum.cloudron.io/post/78343Tue, 28 Nov 2023 10:54:07 GMT<![CDATA[Reply to Getting cloudron auth back on Tue, 28 Nov 2023 10:49:58 GMT]]>@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.

]]>https://forum.cloudron.io/post/78342https://forum.cloudron.io/post/78342Tue, 28 Nov 2023 10:49:58 GMT<![CDATA[Reply to Getting cloudron auth back on Tue, 28 Nov 2023 10:14:49 GMT]]>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.

]]>https://forum.cloudron.io/post/78338https://forum.cloudron.io/post/78338Tue, 28 Nov 2023 10:14:49 GMT<![CDATA[Reply to Getting cloudron auth back on Wed, 22 Nov 2023 07:39:18 GMT]]>Not really , why do you need it though?

]]>https://forum.cloudron.io/post/77919https://forum.cloudron.io/post/77919Wed, 22 Nov 2023 07:39:18 GMT