| Summary: | RFE: Certificate Serial Number is normally in hex, but not so in ipa ui | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Namita Soman <nsoman> |
| Component: | ipa | Assignee: | Rob Crittenden <rcritten> |
| Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | dpal, jgalipea, mkosek |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ipa-2.2.0-5.el6 | Doc Type: | Enhancement |
| Doc Text: |
No documentation needed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 13:15:17 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 756082 | ||
|
Description
Namita Soman
2011-10-13 18:52:37 UTC
Upstream ticket: https://fedorahosted.org/freeipa/ticket/1991 I think we should discuss with CS team for best practices. I think as long as it is clear what type of data it is that is enough. Why this is an RFE? This came up during the SA training, and during the discussion, it was suggested as an RFE fixed upstream. master: d4a80dbe52158f204e78afea742fc3322bbc65e5 d082b64b7b17ceee5fe3e2d7d9140b100ee4ea59 ipa-2-2: b7a7b4cb5e2a5c52fc132e5e2053954829e1be3f 62dc232e3f9d58f8f3bd8f16715f3afcb0bf44ca What you'll see is a separate attribute on output with the value in hex. This will appear in hosts, services and on the cli in the cert commands that display serial number (cert-request, cert-show and cert-revoke). verified and automated tests fixed :: <snip> Serial Number: 8 Serial Number (hex): 0x8 </snip> version: ipa-server-2.2.0-9.el6.x86_64
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No documentation needed.
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. http://rhn.redhat.com/errata/RHBA-2012-0819.html |