@techreport{king-pkix-claimsigning-extn-03,
    number =    {draft-king-pkix-claimsigning-extn-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-king-pkix-claimsigning-extn/03/},
    author =    {Chris Louden and Dave Silver and Matt King and Matt Tebo and Patrick Patterson and Wendy Brown},
    title =     {{claimSigning Extended Key Usage (EKU)}},
    pagetotal = 13,
    year =      2011,
    month =     dec,
    day =       27,
    abstract =  {This document specifies an Extended Key Usage (EKU) value which indicates that the certificate holder is authorized to sign security tokens to assert claims, or attributes, about a subject. When a certificate that asserts the claimSigning EKU signs a claim, the owner of the service holding that certificate is asserting that a statement about the subject is true. For example, a IdP secure token service (STS) would use an X.509 certificate containing the claimSigning EKU to sign SAML assertions containing an identifier and attributes about a user. This EKU value would allow for a separation between the designation that a given Identity belongs within a given Federation, and the empowerment of that entity within the federation to sign claims.. This approach allows for greater flexibility for the operators of Federated systems and for Certification Authorities and avoids the overloading of other, already established methods (such as Assurance Level designation via certificatePolicy OID).},
}