Hello,
We want to devolop a OpenId Server. The server needs to have a (Exposed) endpoint like:https://myenv.outsystems.app/.well-known/openid-configurationBut if I create a application like .well-known the application will be available as wellknownSo we can not use this.In O11 we used the redirect rules for this.
Already created a case at OutSystems but they referred to this forum but here I cannot find a solution here hence this question.
Hope someone can help. Already had a look if I could manage this by DNS but to me that doesn't seems possible.
Regards,
Robert de Vries.
@Robert de Vries : One possible solution is to use a reverse proxy server, such as NGINX. Suppose your OutSystems application is named OIDCServer, and your domain is xyz.com. You would start by configuring your DNS with an A record that points a subdomain like oidcserver.xyz.com to the public IP address of your NGINX server. On the NGINX side, you can then configure a proxy rule to intercept requests to /.well-known/openid-configuration and forward them to your actual OutSystems endpoint, for example https://myenv.outsystems.app/OIDCServer/openid-configuration. This allows you to expose the standard OpenID Connect discovery URL (https://oidcserver.xyz.com/.well-known/openid-configuration) even though OutSystems does not support creating applications or endpoints under the .well-knownpath directly.