Hi, I want to change the hydra_urls_login to my ow...
# talk-hydra
r
Hi, I want to change the hydra_urls_login to my own login page. How do you change the config values from the console?
s
that screen is read-only, but you can change any value using the Ory CLI: https://www.ory.sh/docs/cli/ory-patch-oauth2-config
r
How do I connect to my project from the CLI
s
ory auth
ory get projects
r
Ory get projects seems to not list my project.
s
you can just use
ory patch oauth2-config <project-id>
it should show up in the list, but maybe it is truncated somehow...
r
So is my project ID the "slug"? as I cannot see an Id on the console. Only its name, slug, url etc
s
slug also works
r
getting a forbidden error, is this wrong ?
ory patch oauth2-config ecaaa3cb-0730-4ee8-a6df-9553cdfeef89 \ --replace '/urls/login="http://localhost:7233/login"' The requested action was forbidden
s
are you using the correct account? it has to be the same as on ory console
r
yes same account
I managed to update another config value ok
what it the path to update the hydra_urls_login ?
s
ah you probably cannot set it to localhost
use the Ory proxy or Ory tunnel instead: https://www.ory.sh/docs/guides/cli/proxy-and-tunnel
r
I using the ORY tunnel, I want to set it to my own login page which is currently hosted on localhost
I think the path to the config is the issue as even this fails, ory patch oauth2-config ecaaa3cb-0730-4ee8-a6df-9553cdfeef89 \ --replace '/urls/login="/ui/login"'
s
do you have any details on the error you got?
r
The requested action was forbidden
can you tell me the path to set 'hydra_urls_login' ?
I thought it would be 'urls/login'
s
it should be what you are using, please let me check
r
seems to just give me a forbidden error no matter what the value is
s
I could find your request in our monitoring, the permission check fails suggesting you are using the wrong account that's also why the project does not show up in
ory get projects
r
but this works; ory patch oauth2-config 44829b55-3732-41d3-aeea-1d11cb522934 \ --replace '/strategies/access_token="jwt"'
s
yes but that is another project
one that works with that account
r
ah sorry, I think I gave you wrong command
s
I see errors only for the project ecaaa3cb-0730-4ee8-a6df-9553cdfeef89
r
two mins
silly me, it worked
thanks for your help
s
sure, np
r
my colleague asked yesterday a related question. but hasn't had a response? can you look into this?
Also - if we wanted multiple custom UIs depending on client id - can we support this as the property appears at a global level and is singular ...