# Registry Proxy Authentication

**URL:** <https://discuss.elastic.co/t/registry-proxy-authentication/312460>\
**Category:** Kibana\
**Tags:** fleet\
**Created:** [August 19, 2022, 11:22am UTC](https://discuss.elastic.co/t/registry-proxy-authentication/312460 "2022-08-19T11:22:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zirota](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zirota/32/109876_2.png) [@zirota](https://discuss.elastic.co/u/zirota)\
**Post date:** [August 19, 2022, 11:22am UTC](https://discuss.elastic.co/t/registry-proxy-authentication/312460/1 "2022-08-19T11:22:25Z")

</div>

Hello,

Any idea how I can provide credentials to the proxy specified `xpack.fleet.registryProxyUrl`?

Usually when working with proxies, we make use of the `username:password` basic authentication in the URL such as "[https://username:password@my.proxy.url:8080](https://username:password@my.proxy.url:8080)".  
However, the schema validation validates `xpack.fleet.registryProxyUrl` against a [RFC 3986](http://tools.ietf.org/html/rfc3986) URI, where `username:password` is now deprecated. This results in the schema validation failing.

> <https://github.com/elastic/kibana/blob/main/x-pack/plugins/fleet/server/config.ts#L102>

Currently as a work around, I am overriding the schema and setting the validation for `xpack.fleet.registryProxyUrl` to `schema.maybe(schema.string())`

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 16, 2022, 11:22am UTC](https://discuss.elastic.co/t/registry-proxy-authentication/312460/2 "2022-09-16T11:22:40Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.