Security
  Home arrow Security arrow Page 3 - Trust, Access Control, and Rights for Web Services, Part 2
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBM® developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
VPS Hosting  
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid  
Request Media Kit
Contact Us  
Site Map  
Privacy Policy  
Support  
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
SECURITY

Trust, Access Control, and Rights for Web Services, Part 2
By: Sams Publishing
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 6
    2004-10-12


    Table of Contents:
  • Trust, Access Control, and Rights for Web Services, Part 2
  • The XKMS Services
  • X-KRSS
  • eXtensible Access Control Markup Language (XACML) Specification
  • The XACML Data Model
  • XACML Policy Example
  • eXtensible Rights Markup Language (XrML) Management Specification
  • XrML Use Case Example
  • Summary

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article

     
     
    ADVERTISEMENT


    Trust, Access Control, and Rights for Web Services, Part 2 - X-KRSS
    ( Page 3 of 9 )

    From a Web services point of view, Locate and Validate will be the most common form of XKMS service requested. Depending on the nature of the Web service provided and the security policy in place, X-KRSS messages such as Register, Recover, Revoke, and Reissue may be processed only under a much more stringent environment.

    In the registration phase, as shown in Figure 9.8, an XML application key pair holder registers its public key with a trusted infrastructure via a registration server. The public key is sent to the registration server using a digitally signed request specified by KRSS using the <Register> tag. The registration server responds with an XML formatted confirmation response using the <RegisterResponse> tag, which indicates status of the registration (accepted, rejected, or pending) and a confirmation of name and attribute information registered with the public key. Except in the case of rejection, a key pair identifier is returned in the <RegisterResponse> tag for subsequent referencing purposes. The registration is typically preceded by generation of the key pair in the key pair holder system.

    Trust, Access Control, and Rights for Web Services

    Figure 9.8  X-KRSS key registration.

    A sample X-KRSS <Request> is shown in Listing 9.9.

    Listing 9.9 X-KRSS Request to XKMS Registration Service for Key Registration

    <?xml version="1.0"?>
     <soap:Envelope xmlns:soap="
    http://schemas.xmlsoap.org/soap/envelope/"
     xmlns:soapenc="
    http://schemas.xmlsoap.org/soap/encoding/"
     xmlns:xsi="
    http://www.w3.org/1999/XMLSchema-instance"
     xmlns:xsd="
    http://www.w3.org/1999/XMLSchema"
    xmlns:ds="
    http://www.w3.org/2000/09/xmldsig#">
      <soap:Body>
       <Register xmlns="
    http://www.xkms.org/schema/xkms-2001-01-20">
        <Prototype>
         <Status>Valid</Status>
         <KeyID>mailto:Alice@cryptographer.test</KeyID>
          <ds:KeyInfo>
           <ds:KeyName>mailto:Alice@cryptographer.test</ds:KeyName>
          </ds:KeyInfo>
         <ValidityInterval>
          <NotBefore>2000-09-20T12:00:00</NotBefore>
          <NotAfter>2001-09-20T12:00:00</NotAfter>
         </ValidityInterval>
         <PassPhrase>qfarJIsfcVKLo</PassPhrase>
        </Prototype>
        <AuthInfo>
         <AuthUserInfo>
          <ProofOfPossession>
           <Signature>2PUN8HQlnhf9YI</Signature>
          </ProofOfPossession>
          <AuthKeyBinding>
           <Signature>EfdxSXAidruAszN</Signature>
          </AuthKeyBinding>
         </AuthUserInfo>
        </AuthInfo>
        <Respond>
         <string>KeyName</string>
         <string>KeyValue</string>
        </Respond>
       </Register>
      </soap:Body>
     </soap:Envelope>

    The X-KRSS <RegisterResult> response to this request is shown in Listing 9.10.

    Listing 9.10 X-KRSS Response from the XKMS Registration Service

    <?xml version="1.0"?>
     <soap:Envelope xmlns:soap="
    http://schemas.xmlsoap.org/soap/envelope/"
     xmlns:soapenc="
    http://schemas.xmlsoap.org/soap/encoding/"
     xmlns:xsi="
    http://www.w3.org/1999/XMLSchema-instance"
     xmlns:xsd="
    http://www.w3.org/1999/XMLSchema"
    xmlns:ds="
    http://www.w3.org/2000/09/xmldsig#">
      <soap:Body>
       <RegisterResult xmlns="
    http://www.xkms.org/schema/xkms-2001-01-20">
        <Result>Success</Result>
        <Answer soapenc:arrayType="KeyBinding[1]">
         <KeyBinding>
          <Status>Valid</Status>
          <KeyID>mailto:Alice@cryptographer.test</KeyID>
           <ds:KeyInfo>
            <ds:KeyValue>
             <ds:RSAKeyValue>
    <ds:Modulus>998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oYq7EfdxSXAidruAszNqBoOqfarJ
    IsfcVKLob1hGnQ/l6xw==</ds:Modulus>
              <ds:Exponent>AQAB</ds:Exponent>
             </ds:RSAKeyValue>
            </ds:KeyValue>
            <ds:KeyName>mailto:Alice@cryptographer.test</ds:KeyName>
           </ds:KeyInfo>

          <ValidityInterval>
           <NotBefore>2000-09-20T12:00:00</NotBefore>
           <NotAfter>2001-09-20T12:00:00</NotAfter>
          </ValidityInterval>
         </KeyBinding>
        </Answer>
        <Private/>
       </RegisterResult>
      </soap:Body>
     </soap:Envelope>

    Revocation is handled via a similar protocol. The use of desktop (that is, file system) private key storage—as well as more broad XML client encryption applications—mandates some form of key recovery provision. Key recovery provides a way to recover a lost private key so that corporate-owned data encrypted with the lost private key is not lost forever. For historical reasons, key recovery is not supported by standardized protocols. In X-KRSS, such support is built in.

    SamsThis chapter is from Securing Web Services Security with WS-Security, by Jothy Rosenberg and David Remy (Sams, 2004, ISBN: 0672326515). Check it out at your favorite bookstore today.

    Buy this book now.



     
     
    >>> More Security Articles          >>> More By Sams Publishing
     

       

    SECURITY ARTICLES

    - Critical Microsoft Visual Studio Security Pa...
    - US Faces Tech Security Expert Deficit
    - LAN Reconnaissance
    - An Epilogue to Cryptography
    - A Sequel to Cryptography
    - An Introduction to Cryptography
    - Security Overview
    - Network Security Assessment
    - Firewalls
    - What’s behind the curtain? Part II
    - What’s behind the curtain? Part I
    - Vectors
    - PKI: Looking at the Risks
    - A Quick Look at Cross Site Scripting
    - PKI Architectures: How to Choose One





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 2 Hosted by Hostway
    Stay green...Green IT