OAuth configuration disappearing - and my solution

[ulka]

Hi,

for some months I had the problem that every time I restarted FreeScout the OAuth configuration was gone. The setting was using an OpenID-Client configured in the Cloudron user section.

Now I found out that the app deletes the configuration from the database every time it restarts. It sets up a new configuration which is faulty, the app does not start and displays an error message. I noticed some mysterious characters in the configuration - the Cloudron instance name is used as the OAuth name, and in my instance it contains German characters like ü and Ü in a quite strange coding. The FreeScout OAuth module cannot handle these.

Maybe I am not the only one who has this problem. It would be a great improvement if the name could be made more robust.

[nebulon]

Just released a new package which fixes the issue. The root problem was a missing LANG environment variable which caused some trouble.

[james]

Hello @ulka
Since you describe that this is a FreeScout module issue, did you report it to FreeScout as well?
They might be able to fix this issue with the module.

[joseph]

@ulka is freescout installed with or without Cloudron user management? If it's the latter, that is the most likely issue. Check in App -> Access Control. Does it say User management or Dashboard visibility?

[ulka]

Yes, it's Cloudron user management.

What about the idea of passing a HTML-encoded String containing ü? I don't know which mechanism is used. Does Cloudron save this data directly into the database?

[joseph]

Did I understand correctly that you are setting some custom OpenID config but not using Cloudron management i.e it is not Cloudron OpenID?

If so, you have to switch over the app to not using Cloudron user management since the packaging will pre-configure the app to use Cloudron's own OpenID server. To do this:

• Make an app backup. Then download backup config
• Install a fresh freescout without cloudron user management. Do this in a temp location, do not uninstall your existing freescout .
• Then, new freescout -> backups -> import. Upload the config from step 1
• If things look ok, you can delete the original freescout and change location of this temp freescout .

[ulka]

No, it's almost perfect for me now. The only issue is that Cloudron fails to set a valid configuration if the Cloudron instance name contains unusual characters. If I remove them, all is shiny. (And these characters are quite common in German.)

[nebulon]

Oh so if the Cloudron name contains umlaute, the freescout integration fails? That sounds like an escaping bug in the package start.sh then!

[nebulon]

Ok I can confirm, the app will fail to even startup properly if umlauts are set as a cloudron name! Good catch, will try to fix the package.

[ulka]

I'm looking forward to it. Danke!

[nebulon]

Just released a new package which fixes the issue. The root problem was a missing LANG environment variable which caused some trouble.