Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1651368

Summary: Add documentation for the '-N' option to the dogtag-ipa-renew-agent-submit man page
Product: Red Hat Enterprise Linux 7 Reporter: Marco Rhodes <mrhodes>
Component: certmongerAssignee: Rob Crittenden <rcritten>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.6CC: myusuf, nalin, ndehadra, pvoborni
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: certmonger-0.78.4-12.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-31 19:44:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marco Rhodes 2018-11-19 20:26:42 UTC
Description of problem:

The man page for dogtag-ipa-renew-agent-submit does not describe the '-N' option, which overrides the renewal of an existing serial number (certmonger will instead send the certificate request to be processed ).

Comment 2 Rob Crittenden 2019-05-20 19:15:57 UTC
Fixed upstream in 0.79: c3599704aa02b5c0c2e6f1b155b236707d2418e0

Comment 4 Mohammad Rizwan 2019-12-06 10:42:26 UTC
version:
certmonger-0.78.4-12.el7.x86_64


$ /usr/libexec/certmonger/dogtag-ipa-renew-agent-submit  --help
Usage: dogtag-ipa-renew-agent-submit [options] -E EE-URL -A AGENT-URL [csrfile]
  -E, --ee-url=URL                 end-entity services location
  -A, --agent-url=URL              agent services location
  -i, --cafile=FILENAME
  -C, --capath=DIRECTORY
  -d, --dbdir=DIRECTORY            database containing agent or client creds
  -n, --nickname=NAME              nickname of agent or client creds
  -c, --certfile=FILENAME          agent or client certificate
  -k, --keyfile=FILENAME           agent or client key
  -p, --sslpinfile=FILENAME        agent or client key pinfile
  -P, --sslpin=STRING              agent or client key pin
  -s, --hex-serial=NUMBER          request renewal for certificate by serial number (hexadecimal)
  -D, --serial=NUMBER              request renewal for certificate by serial number
  -o, --submit-option=STRING       key-value pair to send to server
  -O, --approval-option=STRING     key-value pair to set in certificate
  -T, --profile=NAME               enrollment profile
  -t, --profile-list               list enrollment profiles
  -S, --state=STATE-VALUE          previously-provided state data
  -V, --dogtag-version=NUMBER
  -N, --force-new                  prefer to obtain a new certificate                        <<<<<<<<<<<<<<<<<<<<<<
  -R, --force-renew                prefer to renew a certificate
  -a, --agent-submit               submit enrollment or renewal request using agent or client creds
  -u, --uid=USERNAME               submit enrollment or renewal request using user name
  -U, --udn=USERDN                 submit enrollment or renewal request using user DN
  -W, --userpwd=STRING             submit password with enrollment or renewal request
  -w, --userpwdfile=FILENAME       submit password from file with enrollment or renewal request
  -Y, --userpin=STRING             submit pin with enrollment or renewal request
  -y, --userpinfile=FILENAME       submit pin from file with enrollment or renewal request
  -v, --verbose

Help options:
  -?, --help                       Show this help message
  --usage                          Display brief usage message



$ man certmonger-dogtag-ipa-renew-agent-submit
[.]
       -N     Even if an already-issued certificate is available in the CERTMONGER_CERTIFICATE environment variable,  or  a
              serial  number  has  been  provided,  don't attempt to renew a certificate using its serial number.  Instead,
              attempt to obtain a new certificate using the signing request.  The default behavior is to request a  renewal
              if possible.

[.]

Based on above observations, marking the bug as verified.

Comment 6 errata-xmlrpc 2020-03-31 19:44:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1052