Project

General

Profile

Bug #30752

Set sles_auth_token in yum-repository form for synching SLES-repos from SCC

Added by Markus Bucher almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

To sync SLES Repositories from Suse Customer Center an additional authentication-token needs to be added to the repository URL.
With pulp2 it was enough to add `?<TOKEN>` to the end of the repository-url.

Pulp3-RPM requires to supply the token as a separate parameter when creating the Remote: https://pulp-rpm.readthedocs.io/en/latest/workflows/create_sync_publish.html#configuration-for-sles-12-repository-with-authentication

This error occurs when using foreman_scc_manager plugin: https://github.com/ATIX-AG/foreman_scc_manager/issues/43

Associated revisions

Revision 3968c441 (diff)
Added by Justin Sherrill almost 2 years ago

Fixes #30752 - support sles token via url param

this extends the current support for sles tokens (by putting a param
at the end like http://url/path?token) by parsing that token and
passing it to pulp3

History

#1 Updated by Chris Roberts almost 2 years ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.17.0
  • Category set to Repositories

#2 Updated by The Foreman Bot almost 2 years ago

  • Assignee set to Justin Sherrill
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/8928 added

#3 Updated by The Foreman Bot almost 2 years ago

  • Fixed in Releases Katello 4.0.0 added

#4 Updated by Justin Sherrill almost 2 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF