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 1477971 - Two smart card sections can be merged
Summary: Two smart card sections can be merged
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Linux_Domain_Identity_Management_Guide
Version: 7.4
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Marc Muehlfeld
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-03 11:13 UTC by Aneta Šteflová Petrová
Modified: 2019-04-09 10:36 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Aneta Šteflová Petrová 2017-08-03 11:13:26 UTC
23.2. Authenticating to an Identity Management Client with a Smart Card
23.3. Authenticating to an Identity Management System Remotely with a Smart Card

These two sections describe the same use case for ssh authentication. Flo (frenaud) suggested we can merge them -- keep only 23.2.

Comment 4 Marc Muehlfeld 2019-02-28 16:40:44 UTC
Should the whole 
> 23.3. Authenticating to an Identity Management System Remotely with a Smart Card
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/linux_domain_identity_authentication_and_policy_guide/index#auth-remotely-sc
section be removed and 
> 23.2. Authenticating to an Identity Management Client with a Smart Card
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/linux_domain_identity_authentication_and_policy_guide/index#auth-idm-client-sc
be kept?

Or should parts from 23.3 be moved to 23.2 (which ones)?

Comment 5 Florence Blanc-Renaud 2019-03-04 08:26:03 UTC
Hi Marc,
the 23.3 section can be completely removed.
You can take the content from 23.3.4. Authenticating to the Remote System from the Local System to replace the content from 23.2.4. Authenticating on an Identity Management Client with a Smart Card Using SSH, because it is more detailed (it explains also for AD users).
You can also add the content from 23.3.5. Additional Resources to 23.2.5 Additional Resources (the paragraph about obtaining a TGT is missing in 23.2.5).

Comment 8 Marc Muehlfeld 2019-04-09 10:34:02 UTC
Windows Integration Guide, Linux Domain Identity, Authentication, and Policy Guide und System-Level Authentication Guide sind live

Comment 9 Marc Muehlfeld 2019-04-09 10:36:07 UTC
The update is now available on the Customer Portal.


Note You need to log in before you can comment on or make changes to this bug.