The ClientID for OIDC is usually provided and generated by the OIDC Identity provider, but Stalwart insists to use the ClientID stalwart-webui.
Therefore it’s not possible to use Nextcloud with the “OpenID Connect Provider” App as an identity source. I know there are better IDPs, but in my use case (PoC) it’s the best option.
Why it matters. The ClientID must be unique on the identity provider, therefore it’s usually dynamically created by it. Sometimes there are workaround, but to make Stalwart more compatible to existing environments it would be very important to make the ClientID customizable.
thank you for the hint about this pretty new feature. Haven’t found anything in the documentation, so I don’t know if anything else is necessary to get this configuration working.
Only setting this to a custom client id, doesn’t change anything. There is still the old client_id stalwart_webui transmitted to the IDP.
After configuring the client_id, I reloaded the server settings and restarted the whole server.
but I wasn’t able to find any log entry or hint about the WebUI version. From what I think I should run the latest v.1.0.9 version, but as I said, I can’t tell you for sure.
Maybe it would have been enough to execute the management action “update applications” as the latest tag/url points already to the version v1.0.9
Over all you made me happy
The feature request was implemented 2 days before I have asked and you have been very helpful to get it running!
But if I’m allowed to place an improvement… A hint on the directory configuration page about this possible configuration in the Web Applications page would be helpful, as this is actually a configuration you expect to change there.
