Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1677728 - [RFE] allow to invoke without username and password
Summary: [RFE] allow to invoke without username and password
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Bootstrap
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Rich Jerrido
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-15 17:37 UTC by Ivan Windon
Modified: 2022-03-13 17:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-28 14:30:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-8997 0 None None None 2022-03-13 17:28:51 UTC

Comment 1 Rich Jerrido 2019-02-15 19:14:47 UTC 
Why not pass --skip foreman or --content-only.

The API requires authentication via username/password, which is why it is used.
Comment 2 Rich Jerrido 2019-02-18 13:06:55 UTC 
From the README.md (/usr/share/doc/katello-client-bootstrap*/README.md on a Satellite/Capsule)

### Registering a system to Foreman + Katello, for content only.


This usage leverages the `--skip foreman` switch, which does not require username/password authentication.

**NOTES**

 - the `--skip foreman` switch implies `--skip puppet`
 - When using `--skip foreman`, it is expected that the organization specified  (via `--organization|-o`) is specified via **LABEL**, not **NAME**.

Option 1: using the `--skip foreman` option.

~~~
# ./bootstrap.py -s foreman.example.com \
    -a ak_Reg_To_Dev_EL7 \
    -o "Red_Hat" \
    --skip foreman
~~~

Option 2 : using the `--content-only` option. This option exists as an alias to `--skip foreman`.

~~~
# ./bootstrap.py -s foreman.example.com \
    -a ak_Reg_To_Dev_EL7 \
    -o "Red_Hat" \
    --content-only
~~~


I would be willing to, at best, take this as an RFE to make documentation clearer on this usage.
Note You need to log in before you can comment on or make changes to this bug.