Status LDAP integration?

[imc67]

@subven @nebulon @girish is there any news about the LDAP integration? It would be more than welcome as it is confusing for users to have a “non-synchronized” account for this much much used app.

[subven]

@imc67 I bought the LDAP extension but had no luck because I used the LAMP 7.4 package that includes the Cloudron LDAP addon. Sadly the Freescout documentation says PHP 7.3 and below is required because of ldap_control_paged_result() I will keep testing with the Freescout app and report back.

[nebulon]

I took another look at the ldap plugin more in-depth and after much debugging, I managed to get it to work in a hackish way. I don't fully understand all the code paths yet, but I reached out to the upstream devs again to hopefully get this sorted out in a proper way.

I will keep this thread updated on the progress.

[subven]

@nebulon haha okay then you were faster than me. I cloned your ldap branch and started testing two days ago. Thank you for the commitment and the effort!

[nebulon]

We managed to come up with a fix and they have released a new LDAP plugin already which is now compatible.

I am currently fixing up the autoconfiguration and then we can enable optional LDAP support in the package. Of course though this is then a bit special, since installing the app with user management integration also means one has to purchase the FreeScout LDAP plugin afterwards.
I don't think we have any app in our library following that approach for the moment.

[girish]

@nebulon Do freescout plugins work with a license key? If so, is the idea to install with Cloudron authentication and then make the user put in license key for things to start working? Or is it that we cannot put the code at all in the docker image?

Also, the closest we have like this is Confluence.

[marcusquinn]

@girish Yup, 32 varchar licence keys (as opposed to licence files).

[subven]

@girish basically yes. You can only install an module if you have the license key for it. The env's used by an module can be stored in configuration files beforehand. Usage is therefore opt-in and does not affect normal cloudron users without a license.

I like their concept and price model very much and it was easy for me to buy a few (lifetime) module licenses.

[nebulon]

Since I kind of got stuck eventually somewhere in the auth framework, of which I am no expert, we have provided the freescout team a Cloudron to be able to reproduce the login issue.

They have managed to fix this upstream, so I am trying to work out how we can test this with maybe a test license for package updates...once that is resolved we can finally push a package which supports LDAP

[nebulon]

We have published a new app package now, which contains the LDAP fixes.
The app can be installed with cloudron usermanagement now, however that feature only works if the Freescout LDAP module is also purchased. Once it is activated, just restart the app and it should work.

In order to use this, a fresh FreeScout instance has to be installed!

[imc67]

@nebulon this is very good news! Do you have any advice how to migrate an existing app?

[nebulon]

Unfortunately not really. I guess you could try to update your existing, then install a new instance and import a backup from the other into that.
I am not sure though what really happens if user account emails would clash between old and LDAP users in Freescout.

[girish]

@nebulon would be great to migrate our freescout instance also!

[imc67]

@girish said in Status LDAP integration?:

@nebulon would be great to migrate our freescout instance also!

I think I wait with ours until you have experienced

[nebulon]

Alright, we managed to migrate our own instance now. Freescout matches users by email, so it would merge the user profiles from LDAP and built-in. The process is as follows:

1. update your current instance to latest version
2. install LDAP module and activate on old version (if not done already, this can also be done later but since the license key does not work multiple times, this is the safer option)
3. create a fresh backup after LDAP module activation
4. Install a fresh FreeScout app instance on your Cloudron
5. Import the latest backup of your old installation into this app
6. Login to new app and verify things are working
7. You can now uninstall the old app instance and probably relocate the new one to the old domain

[imc67]

@nebulon this is as usual excellent news and way of working in Cloudron!

Tomorrow morning I’ll migrate two instances!

[humptydumpty]

Would the 2FA carry over through LDAP if i switch my freescout instance over to the new version or do I also need to get the freescout 2FA module?

[girish]

This post is deleted!