-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The [keystone_authtoken] www_authenticate_uri option should point public url #217
Comments
I believe nova-api using the public keystone URL for everything: $ oc get -o yaml NovaAPI/nova-api | grep keystoneAuthURL
keystoneAuthURL: http://keystone-public-openstack.apps-crc.testing I think the template parameter name is misleading here: nova-operator/templates/nova.conf Line 196 in cb238f8
But the actual value is coming from here: nova-operator/controllers/nova_controller.go Lines 810 to 814 in cb238f8
So my questions is: Is it OK to use the public endpoint for everything?
|
my intenstion is for nova to use the internal endpoitns of all service it calls but our external links in the API repoce should really be to the endpoint you invoked. so if you call to the internal endpoint it should be internal and external external. |
Do you know how to configure nova to get this behavior? |
i dont think we should have to change the CR we should just take one keystone URL and that should be the internal one although we can always use endpoint to lookup the internal one too programmatically regardless of what is passed by the user in the cr. for 2 no i thought we looked at the URL used to make the query to determine how we render the refurls in the responce. |
Sorry I was confused by that naming ( Jusy FYI. If we want nova to use internal endpoint for keystone API call, what we'd need are
However even in that case |
OK I can make that change without CR change. I will pass only the internal URL to NovaAPI. |
AFAIK we have to configure www_authenticate_uri, otherwise the middleware returns wrong url (likely http://127.0.0.1:35357 ). |
Based on the config doc we have to pass the public url so I will propose a patch to fix this. |
According to the keystone middleware doc we have to set www_authenticate_uri to the public keystone endpoint as an unauthenticated user is redirected to this URL. Our service uses the internal endpoint for auth and so far it used the internal endpoint for www_authenticate_uri as well. But this will not work for external users. A new field is added to the NovaAPI CR to allow configuring not just the internal endpoint but also the public endpoint. Closes: openstack-k8s-operators#217
According to the keystone middleware doc we have to set www_authenticate_uri to the public keystone endpoint as an unauthenticated user is redirected to this URL. Our service uses the internal endpoint for auth and so far it used the internal endpoint for www_authenticate_uri as well. But this will not work for external users. A new field is added to the NovaAPI CR to allow configuring not just the internal endpoint but also the public endpoint. Closes: openstack-k8s-operators#217
According to the keystone middleware doc we have to set www_authenticate_uri to the public keystone endpoint as an unauthenticated user is redirected to this URL. Our service uses the internal endpoint for auth and so far it used the internal endpoint for www_authenticate_uri as well. But this will not work for external users. A new field is added to the NovaAPI CR to allow configuring not just the internal endpoint but also the public endpoint. Closes: #217
Currently the
[keystone_authtoken] www_authenticate_uri
option points internal url, but this should point public url, because the url is returned to clients when auth request fails.We probably have to add separate options for public/internal endpoint and use different endpoints accordingly.
The text was updated successfully, but these errors were encountered: