You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Login in the demo should fail as the user gets redirected to http://this.domain.does.not.exist.and.is.invalid.
The value of urls.self.public should be used for everything except well-known paths, as the intent of this configuration setting is to tell Hydra the URL that points to itself.
However, right now all of the paths use urls.self.public with the exception of the /userinfo path. RFC 8414, section 2, requires that metadata be published at a well-known address at the issuer. However, no such mandate is made for the other endpoints.
Environment
This issue is environment agnostic.
Additional context
Addressing this issue allows for using, among other things, urn-URIs as issuer, which are useful in contexts where publishing metadata is not required.
The text was updated successfully, but these errors were encountered:
Describe the bug
Reproducing the bug
Steps to reproduce the behavior:
hydra
inquickstart.yml
:URLS_SELF_PUBLIC=http://this.domain.does.not.exist.and.is.invalid
Server logs
Not relevant
Server configuration
Expected behavior
Login in the demo should fail as the user gets redirected to
http://this.domain.does.not.exist.and.is.invalid
.The value of
urls.self.public
should be used for everything except well-known paths, as the intent of this configuration setting is to tell Hydra the URL that points to itself.However, right now all of the paths use
urls.self.public
with the exception of the/userinfo
path. RFC 8414, section 2, requires that metadata be published at a well-known address at the issuer. However, no such mandate is made for the other endpoints.Environment
This issue is environment agnostic.
Additional context
Addressing this issue allows for using, among other things,
urn
-URIs as issuer, which are useful in contexts where publishing metadata is not required.The text was updated successfully, but these errors were encountered: