Best practices or possibilities for 2-way / app-to-Cloudron user creation and management (LDAP/Directory/OpenID)

[xarp]

I feel like this idea has probably been discussed or presented. But perhaps I'm thinking of it in a way that's making me foggy on locating the clearest answer.

Scenario:

• WordPress is the front facing website
• The WordPress is running on Cloudron, which is also running a bunch of other apps
• You want users to be able to register an account via your front facing WordPress and in turn have a Cloudron account provisioned to provide 'membership authenticated' access to xyz apps via LDAP/SSO/etc.

IE a membership walled garden (with Cloudron acting as identity provider) for your installed apps that can be handled/automated/interfaced with via WordPress public front end and subsequent subscription management/payment plugins. Kind of like two-way synchronised LDAP.

What would be the best practice and direction to go in this instance? I'm pondering over possibilities in the directory server section of docs page.

The most 'traditional' method of doing this, in my mind, involves a CRM with n8n type automation to achieve what's desired.. But I'm thinking if this can all be drastically simplified by all being in the same Cloudron ecosystem.

(I'm aware not all apps support centralised account management, instead managed individually at app level, and this would be another hurdle.)

Drop me your thoughts and help set my mind straight. Thanks!

[micmc]

The idea is good, only I would more opt for a Cloudron front-end registration UI, than through WordPress.

Not eveyone use WP, so they would be forced to install it to take advantage of this function. Moreover, this would work the other way around and still accomplish what you want.

On Cloudron, WordPress can be installed in a manner to automatically provide accounts access to its dashboard, to each Cloudron users you chose (individually and via groups).

That would make much more sense inho, and still accomplish what you desire like adding those users to specific membership access within WordPress, payment system etc.

Hope that helps you clear it a little

[xarp]

Thanks for the response and input. Albeit one side note is that this post is more of a specific implementation that I'm considering based on my objectives, and initially less about a general 'feature suggestion'. Although it seems my idea does certainly invoke the feature suggestion aspect too. And now I'm glad I posted.

As it stands currently, I think you're probably right about the best way to implement this concept. The downside, however, is I'd likely need to hire a dev to conjure up an API based registration page to feed Cloudron. It's just not my skill set. The WordPress component would have negated that and as such was a primary benefit of using it, in addition to the full subscription management and fiat/crypto payment capabilities that come along with its extensibility.

Appreciate the insight

[micmc]

Yes, of course you've put the finger on it. Having a dev to develop a UI to add the WP users to Cloudron through API, should not be too complicated in fact. If you absolutely want to go that route, of course.

Good luck, and above all have fun!

[plusone-nick]

@xarp in the past I had built a custom php app that did exactly what you’re asking for. A simple registration page for a Cloudron user. I plan on implementing some form of group allocation and eventually subscription/payments.

If you’d like we can talk about me making you a custom version of the app