-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Registry Proxy URL not working with authentication #100518
Comments
Pinging @elastic/fleet (Team:Fleet) |
@jfsiii Do you happen to know if the registry proxy support we added supports auth? |
@jen-huang Yes, or at least that was the intent. We added that in https://github.com/elastic/kibana/pull/89071/files and included some unit tests. However, since https://epr.elastic.co/ does not return I believe we have the correct settings for the node transport, but perhaps not. @CruzMarcio can you provide any other information or logs about what requests the proxy is "seeing"? Or even just any details about how you're proxying. Any additional information is appreciated. Thanks. |
Hi @jfsiii . The only error I see on the Kibana logs is the one below. If there is any way to get more logs on this let me know.
|
Hi @CruzMarcio I am starting to work on this, can I get a little more information on what software are you running as a proxy? also for actions do you have any |
Hi @nchaulet. |
@CruzMarcio Can you see/share any logs from the proxy at that address? No code in Kibana or the Registry will return a Either way, a All my local testing (and some unit tests) indicates that the username and password are passed to the proxy as expected. For example, the actions plugin ships with a forward proxy for testing
Note the
Perhaps the proxy expects the username & password to come from something that HTTP Basic Authorization ( |
Closing as not relevant anymore. Feel free to reopen if needed |
Hello, attempting to close the loop here... Credentials can be provided via Filed a doc issue at elastic/ingest-docs#1722 |
Kibana version: 7.12.1
Elasticsearch version: 7.12.1
Describe the bug:
Getting an "Unable to initialize Fleet" error on the fleet home screen with the details: "'407 Proxy Authentication Required' error response from package registry at https://epr.elastic.co/search?package=system&internal=true&experimental=true&kibana.version=7.12.1"
I've set the xpack.fleet.registryProxyUrl configuration to "http://user:password@proxy:80", the same one as the xpack.action.proxyUrl which is needed to send Webhook connectors but it dose not seem to work for fleet.
Steps to reproduce:
Set the xpack.fleet.registryProxyUrlproperty on the kibana.yml file to the a proxy address with authentication like "http://user:password@proxy:80"
Access the fleet home screen at http://kibana:5601/app/fleet#/
Get the error "'407 Proxy Authentication Required' error response from package registry at https://epr.elastic.co/search?package=system&internal=true&experimental=true&kibana.version=7.12.1"
Expected behavior:
Fleet should load without errors.
The text was updated successfully, but these errors were encountered: