Hi Tobias.

The repo is not reaching by this exact URL, but the path to repodata usually appended to get the exact files.

For example likg this:

https://HOST.DOMAIN.TLD:443/rhn/manager/download/sle-module-legacy15-sp1-updates-x86_64/repodata/repomd.xml?eyJhbGciOiJIUzI1NiJ9.eyJleHAiOjE2MzQ5ODE5NDAsImlhdCI6MTYwMzQ0NTk0MCwibmJmIjoxNjAzNDQ1ODIwLCJqdGkiOiIzQS1PbmpjanMtQXFETmZqVTJkTU93Iiwib3JnIjoxLCJvbmx5Q2hhbm5lbHMiOlsic2xlLW1vZHVsZS1sZWdhY3kxNS1zcDEtdXBkYXRlcy14ODZfNjQiXX0.H203CwoN5ns0YUnzZMmd

Note the changes with the URL you provided.

But the case you are describing is more like you need to detokenize the repos. It could be done with setting `java.salt_check_download_tokens = false` to /etc/rhn/rhn.conf

With this setting you can get an access to repo with no token checking like https://HOST.DOMAIN.TLD:443/rhn/manager/download/sle-module-legacy15-sp1-updates-x86_64/repodata/repomd.xml

Regards,

Victor

On Fri, 2021-05-14 at 14:51 +0200, Tobias Crefeld wrote:

Hi,

I have several systems (SLES + opensuse) that have no access to the

public internet but to our Uyuni system. Unfortunately we're not

allowed to install a client software on these systems, so a regular

system integration by Uyuni is not possible.

On the other hand it is possible to edit the client's repository

configuration ( /etc/zypp/repos.d/ manually.

With a standard webserver that is regularly mirrored to a public

repository this is no problem, but if I look at our typical salt

clients I find baseurls like

baseurl=https://HOST.DOMAIN.TLD:443/rhn/manager/download/sle-module-legacy15-sp1-updates-x86_64?eyJhbGciOiJIUzI1NiJ9.eyJleHAiOjE2MzQ5ODE5NDAsImlhdCI6MTYwMzQ0NTk0MCwibmJmIjoxNjAzNDQ1ODIwLCJqdGkiOiIzQS1PbmpjanMtQXFETmZqVTJkTU93Iiwib3JnIjoxLCJvbmx5Q2hhbm5lbHMiOlsic2xlLW1vZHVsZS1sZWdhY3kxNS1zcDEtdXBkYXRlcy14ODZfNjQiXX0.H203CwoN5ns0YUnzZMmd

Using these URL in a webbrowser returns 4xx - errors.

Is there any way to provide the respective clients a standard path

like http://download.opensuse.org/distribution/leap/15.2/repo/oss/ to

the Uyuni server?

Or is there any other way to provide Uyuni's repositories to these

"clients" without installing special software at the client side?

TIA!