Back to bug 1402959
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2016-12-08 18:40:18 UTC | Keywords | FutureFeature | |
| Martin Kosek | 2016-12-09 10:05:11 UTC | Blocks | 1399979 | |
| Martin Kosek | 2016-12-16 11:25:30 UTC | Priority | unspecified | high |
| CC | mkosek | |||
| Summary | [RFE] Certificate Identity Mapping | [RFE] Universal Smart Card to Identity mapping | ||
| Libor Miksik | 2017-01-10 16:01:59 UTC | Blocks | 1411849 | |
| Libor Miksik | 2017-01-10 16:04:53 UTC | Blocks | 1411852 | |
| Libor Miksik | 2017-01-10 16:11:01 UTC | Blocks | 1411858 | |
| Tomas Krizek | 2017-03-08 09:19:27 UTC | CC | tkrizek | |
| David Kupka | 2017-03-08 15:26:28 UTC | Status | NEW | POST |
| CC | dkupka | |||
| Jan Pazdziora | 2017-03-09 09:25:29 UTC | CC | jpazdziora | |
| Jan Pazdziora | 2017-03-09 09:44:14 UTC | Depends On | 1430675 | |
| Jan Cholasta | 2017-03-13 07:59:01 UTC | CC | jcholast | |
| Aneta Šteflová Petrová | 2017-03-14 11:48:52 UTC | Blocks | 1430653 | |
| Jan Cholasta | 2017-03-15 17:18:24 UTC | Status | POST | MODIFIED |
| Fixed In Version | ipa-4.5.0-1.el7 | |||
| errata-xmlrpc | 2017-03-15 17:35:53 UTC | Status | MODIFIED | ON_QA |
| Tomas Krizek | 2017-03-28 16:25:36 UTC | Status | ON_QA | POST |
| Jan Cholasta | 2017-03-28 17:35:15 UTC | Status | POST | MODIFIED |
| Fixed In Version | ipa-4.5.0-1.el7 | ipa-4.5.0-3.el7 | ||
| errata-xmlrpc | 2017-03-29 08:38:41 UTC | Status | MODIFIED | ON_QA |
| Tomas Krizek | 2017-03-29 08:42:30 UTC | Status | ON_QA | POST |
| Jan Cholasta | 2017-04-05 08:11:17 UTC | Status | POST | MODIFIED |
| Fixed In Version | ipa-4.5.0-3.el7 | ipa-4.5.0-5.el7 | ||
| errata-xmlrpc | 2017-04-05 08:14:18 UTC | Status | MODIFIED | ON_QA |
| Aneta Šteflová Petrová | 2017-04-27 08:11:43 UTC | Docs Contact | apetrova | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Scott Poore | 2017-05-05 17:03:22 UTC | CC | spoore | |
| Namita Soman | 2017-05-08 13:32:29 UTC | CC | nsoman | |
| QA Contact | ksiddiqu | spoore | ||
| Namita Soman | 2017-05-08 17:55:34 UTC | CC | ipa-qe | |
| Aneta Šteflová Petrová | 2017-05-11 16:00:09 UTC | Doc Text | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. | |
| Flags | needinfo?(pvoborni) | |||
| Petr Vobornik | 2017-05-12 07:39:26 UTC | CC | frenaud | |
| Flags | needinfo?(pvoborni) | |||
| Aneta Šteflová Petrová | 2017-05-12 11:26:40 UTC | Doc Text | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. |
| Aneta Šteflová Petrová | 2017-05-18 10:36:07 UTC | Doc Text | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/smart-cards-advanced.html#flexible-sc-identity-mapping. |
| Scott Poore | 2017-05-19 19:49:36 UTC | Status | ON_QA | VERIFIED |
| Tomas Krizek | 2017-05-26 12:36:37 UTC | CC | tkrizek | |
| Lenka Špačková | 2017-06-30 09:21:48 UTC | Doc Text | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/smart-cards-advanced.html#flexible-sc-identity-mapping. | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/smart-cards-advanced.html#flexible-sc-identity-mapping. |
| Aneta Šteflová Petrová | 2017-07-04 12:22:34 UTC | Doc Text | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/smart-cards-advanced.html#flexible-sc-identity-mapping. | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/sc-one-card-multiple-accounts-links. |
| Marc Muehlfeld | 2017-08-01 06:25:56 UTC | Doc Text | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/sc-one-card-multiple-accounts-links. | IdM supports flexible mapping mechanisms for linking smart card certificates to user accounts Previously, the only way to find a user account corresponding to a certain smart card in Identity Management (IdM) was to provide the whole smart card certificate as a Base64-encoded DER string. With this update, it is possible to find a user account also by specifying attributes of the smart card certificates, not just the certificate string itself. For example, the administrator can now define matching and mapping rules to link smart card certificates issued by a certain certificate authority (CA) to a user account in IdM. For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/smart-cards.html#sc-one-card-multiple-accounts-links. |
| errata-xmlrpc | 2017-08-01 09:44:33 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-08-01 05:44:33 UTC |
Back to bug 1402959