Option to customise `/.well-known/openid-configuration`

[sindre-nistad]

Summary

I'd like to be able to customise the resulting JSON given by /.well-known/openid-configuration.

Desired solution

Something slimilar to the existing Events

server.service.once(Events.BeforeWellKnownDocument, callback)

As long as the callback as access to the document, and is able to either replace it or mutate it, I'm happy.

Alternative solutions

I've tried adding a route with /.well-known/openid-configuration while configuring the server to have a different wellKnownDocument endpoint.

Additional Context

My usecase is running oauth2-mock-server in a container with oauth2-proxy so we have automatic redirect to the url defined by authorization_endpoint as defined in /.well-known/openid-configuration.
In this case, I'd like that to be a link to localhost rather than the issuer URL.

[nulltoken]

@sindre-nistad Thanks for opening this issue.

One question: would changing the issuer url be enough in your use case (to https://whatever.com or http://localhost for instance)?

IOW, if the authorization_endpoint was exposing "https://whatever.com/authorize", would that fit your need?

const server = new OAuth2Server();
server.issuer.url = 'https://whatever.com';

[sindre-nistad]

One question: would changing the issuer url be enough in your use case (to https://whatever.com or http://localhost for instance)?

Unfortunately, no, as that would cause the Oauth2-proxy, and other containers to try to access their localhost rather than the container running oauth2-mock-server.
It is possible with some socat shenanigen, but I'd rather not.

IOW, if the authorization_endpoint was exposing "https://whatever.com/authorize", would that fit your need?

That would work, as it is essentially what I wanted to accomplish

[nulltoken]

IOW, if the authorization_endpoint was exposing "https://whatever.com/authorize", would that fit your need?

That would work, as it is essentially what I wanted to accomplish

Could you please try changing the issuer url in your context and report the outcome?

const server = new OAuth2Server();
server.issuer.url = 'https://whatever.com';

[sindre-nistad]

IOW, if the authorization_endpoint was exposing "https://whatever.com/authorize", would that fit your need?

That would work, as it is essentially what I wanted to accomplish

Could you please try changing the issuer url in your context and report the outcome?

const server = new OAuth2Server();
server.issuer.url = 'https://whatever.com';

I've tried, but unfortunately that causes our oauth2-proxy container to try to fetch http://localhost8080/.well-known/openid-configuration which does not exist as far as that container is concered. That container expected to fetch it from http://container-name:8080.

It would work if https://whatever.com was visible to both containers, and the host's web browser, ubt using an external domain is (unfortunately) not an option in this usecase

[nulltoken]

@sindre-nistad Ok. Let's go the event way then.

Maybe something like the following?

Events.BeforeWellKnownOpenIdConfiguration
Typed signature: (openIdConfigurationResponse: MutableResponse, req: IncomingMessage) => void

Would you feel like contributing this feature?

[sindre-nistad]

@sindre-nistad Ok. Let's go the event way then.

Maybe something like the following?

Events.BeforeWellKnownOpenIdConfiguration
Typed signature: (openIdConfigurationResponse: MutableResponse, req: IncomingMessage) => void

Would you feel like contributing this feature?

I might be able to contribute; I'll look into it