What's coming in 7.7

[girish]

We want to get releases out earlier. A bunch of things are already implemented, so we will release 7.7 in the coming days.

Features & Fixes:

• OIDC avatar support
• mongodb: Update mongodb to 6.0
• port range support for apps like MiroTalk
• oidc/ldap: fix display name parsing to send anything after first name as the last name
• mail: Update haraka to 3.0.3
• acme: use secp256r1 curve for max compatibility
• docker: disable userland proxy
• mail: update solr to 8.11.3
• mail: spam acl should allow underscore and question mark
• Fix streaming of logs with logPaths
• profile: store user language setting in the database

[imc67]

Don’t forget the patch for https://forum.cloudron.io/post/81829

[girish]

@imc67 yes, it's already in it!

[jdaviescoates]

@girish said in What's coming in 7.7:

port range support for apps like MiroTalk

Will this mean Cloudron will be able to support MiroTalk Web/ SFU (and not just MiroTalk P2P like at present)?

[girish]

@jdaviescoates yes, it's specifically for the SFU!

[jdaviescoates]

@girish said in What's coming in 7.7:

@jdaviescoates yes, it's specifically for the SFU!

Great!

[lukas]

Immich update will be also available with 7.7?

[girish]

@lukas yes, postgres is also updated already with latest vectorRS extension for immich.

[lukas]

When will be Cloudron 7.7 released?

[girish]

I was mistaken about the postgres fixes for immich. @nebulon is still working on this. Once that is done , 7.7 can be released. Probably in a day or two.

[nebulon]

It is taking much longer than expected, as immich now needs superuser database permissions for certain sql commands, which are not granted on Cloudron for security and database isolation issues, so will see how far I can get for 7.7.

[nebulon]

To update here, for immich we are still trying to work out this issue: https://github.com/immich-app/immich/issues/7626

[sponch]

@girish very cool! Waiting for release

[sponch]

Update is available Now waiting for MiroTalk SFU

[shrey]

Seems to be an unstable release still.

---

I guess the stable release will take some more time.

[p44]

@girish about this point: "oidc/ldap: fix display name parsing to send anything after first name as the last name" ... I think logic has to be analyzed again... because is not working as described. Eg. "Willem van Oranje", after this update, becomes "Willem Oranje"... ("Van" is lost)

[girish]

@p44 yeah ,I think for that to be done correctly we have to take first name/last name as proper separate fields. Current logic is too simplistic.

[imc67]

@girish this was noticed and discussed more than a year ago … https://forum.cloudron.io/topic/8345/cloudron-ldap-middle-name-not-correctly-propagated

[girish]

@imc67 @p44 so, in 7.7 atleast, we did something like this:

+            const names = [
+                { in: 'James', out: { firstName: 'James', lastName: '', middleName: '' } },
+                { in: 'James Anderson', out: { firstName: 'James', lastName: 'Anderson', middleName: '' } },
+                { in: 'James Philip Anderson', out: { firstName: 'James', lastName: 'Philip Anderson', middleName: '' } },
+            ];

So, Willem van Oranje would be parsed as firstName Willem and lastName van Oranje. While not correct , atleast all the parts of the name are delivered to the app. Pre 7.7, parts of the name were dropped. I am wondering why app uses middlename now. What app are you testing with ?

[girish]

In Grafana, my names shows correctly, for example:

Note that it could also be that the app in question is not updating the name on OIDC re-login.