simplify oCIS deployment with external IDP #2819
Labels
Category:Enhancement
Add new functionality
Category:Technical
Technical ehancements
Estimation:S(2)
Interaction:Needs-Concept
Is your feature request related to a problem? Please describe.
When you are using oCIS with an external IDP, you need to make sure, that oC Desktop / iOS / Android clients can find the
.well-known/openid-configuration
endpoint on the same domain / port, in general address as oCIS.This endpoint is provided by an external IDP in our case. Redirects to this proxy are not allowed (OIDC spec), therefore we need to proxy requests to the IDP. The current capabilities of the proxy are not sufficient for common usecases. An example for that is our Keycloak deployment example:
ocis/deployments/examples/ocis_keycloak/docker-compose.yml
Lines 130 to 138 in 38d670f
In that example this mapping is done in the proxy:
X-Forwarded-Host
tokeycloak.owncloud.test
since the request originally was to https://ocis.owncloud.test/.well-known/openid-configuration and would have resulted inocis.owncloud.test
Describe the solution you'd like
Have a simple way to make the
.well-known/openid-configuration
endpoint available without using an external proxy.Describe alternatives you've considered
Providing different way to discover the OIDC provider to the clients (eg. like Web with a config) but that would break existing clients.
The text was updated successfully, but these errors were encountered: