Question: Need different domains from metadata response
See original GitHub issueDue to some unfortunate infrastructure we have the server hosted on one domain and the Cypress browser accessing it from another domain.
Dotnet allows me to specify a URL to get the metadata but that response needs to contain url that the browser can use.
response:
{
issuer: "http://localhost:5070/.well-known/openid-configuration",
authorization_endpoint: "http://localhost:5070/.well-known/openid-configuration/authorize",
...
Issue Analytics
- State:
- Created a year ago
- Comments:16 (9 by maintainers)
Top Results From Across the Web
Create a FAQ bot for multiple categories with Azure Bot Service
In this tutorial, you learn how to: Create a project and tag question answer pairs into distinct categories with metadata; Create a separate...
Read more >How can we deploy custom My Domain name via metadata API?
1 Answer 1 · But I can go into Setup > My Domains and change to a new domain. · @VarunC Oh. ·...
Read more >Questions Metadata Can Answer - TDAN.com
– Do the attributes have restrictive domains? – What are the allowable values for the attributes? – What is the relationship between the...
Read more >Meta Info Question - Qualtrics
The meta info question does not require any special editing or preparation. Simply add it to any page of your survey that every...
Read more >Leveraging Structured Metadata for Improving Question ...
We show that leveraging metadata information from web pages can improve the performance of models for answer passage selection/re- ranking.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ybelMekk The problem with Host header is that it is not longer supported to change it since JDK 12 (https://bugs.openjdk.org/browse/JDK-8213696).
Would it be possible to fix host of the metadata (or only the issuer) to a particular value with a config parameter? I think it would be necessary in this kind of scenarios.
It sounds useful yes, but the container, when requesting metadata e.g. a call to
curl http://oauth2:8080/default/.well-known/openid-configuration
gives:then you call the jwks endpoint:
curl http://oauth2:8080/default/jwks
you will get some data, but if you say change the well known metadata issuer to:yolo
you’ll get what you want
but a curl to “http://yolo:8080/default” will give you
curl: (6) Could not resolve host: yolo
So host of container and returned metadata must match, but we could set the issuer and metadata issuer to SERVER_HOSTNAME value as specified.