oauth2 login in config.json overwritten by oidc of cloudron?

[nebel]

Hi,
my hedgedoc is configured with oauth2 in config.json. I had to stop updating hedgedoc, because login is broken since cloudron switched hedgedoc to oidc. I could login via OAuth2 or LDAP before. Now I only have one option called "Cloud". It throws an Error 500 in the callback.
The callback URL contains the domain name of my cloudron server instead of the external oauth2 service.
Any ideas?

[girish]

@nebel Did I understand correctly that you want to use Hedgedoc but with another OIDC provider (i.e not cloudron's OIDC) ?

[nebel]

Yes, that's the way I am using it already. But I had to block updating the app to keep the last 'ldap-version', which is no solution for the long run.

[nebulon]

We have to update the package to support optionalSso so your custom auth provider is not overwritten on restart.

[nebel]

Sounds perfect.

[girish]

@nebel I have pushed optionalSso support. You have to do something like this:

• Backup your current app. Download the backup configuration
• Install the latest packages of HedgeDoc . When installing, install with no sso
• Import your backup from step 1. Backups -> Import
• Email login is enabled by default. So maybe you want to disable that and enable your sso provider.

[nebel]

Thanks a lot! This did solve my problem.
I wonder, if there is anyone, who had oidc and cloudron users before. I think he would lose users in this case. Is it a special case with hedgedoc or is it a problem for all apps?
Anyway, I am happy that my problem is solved.

[girish]

@nebel said in oauth2 login in config.json overwritten by oidc of cloudron?:

I wonder, if there is anyone, who had oidc and cloudron users before. I think he would lose users in this case. Is it a special case with hedgedoc or is it a problem for all apps?

Right, this depends on the app. Some apps can only have one authentication provider active at a time. Others can have multiple authentication providers. I think HedgeDoc supports multiple auth providers be active at a time but only one OIDC provider at a time, looks like. But generally, most of our users do not mix "private" authentication and "public" instance with external users.