I was trying to update the Ory config ```./ory up...
# general
p
I was trying to update the Ory config
Copy code
./ory update identity-config --project .... --file ....
But I get the following error,
Copy code
The request was malformed or contained invalid parameters
  Expected URL but got error `publicsuffix: cannot derive eTLD+1 for domain "0.0.0.0"` while parsing `<http://0.0.0.0:9080>`.
the http://0.0.0.0:9080 was in the original configuration
m
you get the error because
<http://0.0.0.0:9080>
is not a valid public domain what do you mean by "was in the original configuration"?
p
as in the configuration I downloaded when I callled
./ory get identity-config --project ...
It is also the configuration that worked in our CI/CD environment, so saying it is invalid is, IMO, not exactly correct. Why does it have to be a public domain? Can you tell me when that rule was added?
m
Can you tell me when that rule was added?
I believe it was added here https://changelog.ory.com/announcements/ory-network-ory-kratos-v26-1-13-released Which field exactly holds http://0.0.0.0:9080 ?
p
So, quite recently, then, we've had these settings for a number of years. default_browser_return_url and also an entry in the array of allowed_return_urls I am looking to change it as a recent feature is having trouble with http://0.0.0.0:9080 (crypto.subtle) Trying to see if I was on the right track, I altered the entries, thinking I could change them back again to the original settings after testing
I'd like to set the settings back to their original state, as I am reverting my plan and avoiding the use of the API, which is causing me grief.
m
hm this is what I found as a note on the PR
Callback and redirect URLs now reject dangerous schemes (
javascript:
,
data:
,
file:
, custom schemes). Only allow: no scheme,
http
,
https
.
so I guess your URL should work? I'll check with the dev team, see what they say.
p
thanks
Sorry - been away this weekend as we had a public holiday - did you get any progress with the dev team?
@magnificent-energy-493 I got the test in CI to work with the new settings so we have no urgent need to revert our settings now - but the change to disable 0.0.0.0 may need reviewing - there may be others using that setting for their ci/cd and may not be able to alter their tests