Back to bug 1030473
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| John Matthews | 2013-11-14 14:12:48 UTC | Status | NEW | MODIFIED |
| Target Release | --- | 2.1.3 | ||
| Ina Panova | 2013-11-14 16:36:29 UTC | CC | ipanova | |
| John Matthews | 2013-11-18 15:35:02 UTC | Status | MODIFIED | ON_QA |
| Vitaly Kuznetsov | 2013-11-19 13:51:30 UTC | Status | ON_QA | VERIFIED |
| CC | vkuznets | |||
| Cecilee Billett | 2013-12-03 23:08:39 UTC | CC | cbillett | |
| John Matthews | 2013-12-10 16:03:35 UTC | Doc Text | Feature: Added ability for RHUA to read a Red Hat v3 entitlement certificate. Reason: Red Hat is moving to a 'v3' version of encoding entitlement data in a cert. The 'v3' format allows more entitlement data to be stored in a cert and is the future direction. Result (if any): Customers are now able to input a Red Hat v1 or v3 entitlement certificate into RHUA and the entitlements will be read correctly. | |
| Doc Type | Bug Fix | Enhancement | ||
| Megan Lewis | 2013-12-16 02:07:56 UTC | CC | melewis | |
| Doc Text | Feature: Added ability for RHUA to read a Red Hat v3 entitlement certificate. Reason: Red Hat is moving to a 'v3' version of encoding entitlement data in a cert. The 'v3' format allows more entitlement data to be stored in a cert and is the future direction. Result (if any): Customers are now able to input a Red Hat v1 or v3 entitlement certificate into RHUA and the entitlements will be read correctly. | This update adds the ability for RHUA to read a Red Hat v3 entitlement certificate. Red Hat is moving to a 'v3' version of encoding entitlement data in a certificate because the 'v3' format allows more entitlement data to be stored. Customers are now able to input a Red Hat v1 or v3 entitlement certificate into RHUA and the entitlements will be read correctly. | ||
| errata-xmlrpc | 2013-12-17 16:06:00 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2013-12-17 20:11:01 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-12-17 15:11:01 UTC |
Back to bug 1030473