Freedom The Open Source Way Contribute Articles or News to OSForgeOSForge HomeLogout from Forums
Contacting OSForgeOSForge HomeAbout OSForge
  

Root
Contribute News
Learning Corner
Linux Distributions
Linux Common FAQ's
Discussion Forums
Community Gallery
Links Directory
Search OSForge
Networking
Industry Updates
Linux & Open Source
Opinions
Press Release
Programming
Security
Web Development

White Paper
Zarafa and LPI Partner on Training and Certification Program
Likewise to Grow Seattle-Area Workforce
Likewise CTO: Unleash and Secure Unstructured Data
Likewise Names Leading Open Source Voice as CTO
Launched: Zarafa Collaboration Platform 7.0 and Zarafa Archiver
Zarafa Shows User Driven Innovation at Fifth SummerCamp Anniversary
Userful Corporation Named to Everything Channel’s CRN Virtualization 100 List
Zarafa Joins Microsoft with Advanced Outlook 2010 Compatibility
Zarafa and Mandriva Partner to Deliver Integrated Enterprise Solutions

View More »

internetnews.com: Web Services Authentication Takes Leap Forward
By : Victoria Nesta Find more article by Victoria Nesta on Interne
Tuesday the 18th, February 2003 at 06:04 PM (EST)
Send this Story to a Friend Readers TalkBack (0) - 3714 Reads

Printer Friendly Page Printable format
Send this Story to a Friend Foward to Email

The OASIS standards consortium Tuesday took another leap forward toward securing Web services with the ratification of Extensible Access Control Markup Language 1.0 (XACML) as an OASIS Open Standard.

XACML is a security standard which allows developers to write and enforce information access policies, making it a key component in the development of authorization infrastructures and a foundational step in the creation of federated authentication environments.

The XACML specification describes both an access control policy language (which allows developers to specify who can do what and when), and a request/response language which expresses queries about whether a particular access should be allowed and describes the answers to those queries.

In a typical XACML usage scenario, a subject (e.g. human user, workstation) wants to take some action on a particular resource. The subject submits its query to the entity protecting the resource (e.g. file system, web server). This entity is called a Policy Enforcement Point (PEP). The PEP forms a request (using the XACML request language) based on the attributes of the subject, action, resource, and other relevant information. The PEP then sends this request to a Policy Decision Point (PDP), which examines the request, retrieves policies (written in the XACML policy language) that are applicable to this request, and determines whether access should be granted according to the XACML rules for evaluating policies. That answer (expressed in the XACML response language) is returned to the PEP, which can then allow or deny access to the requester.

Full Story


  
Reader Rating from 1-5

 

Poor very 

1

2

3

4

5
 very Excellent

Talkback

Post Your Talkback | View All Talkback (0 Posted)


 Currently there are no Talkback posted on "internetnews.com: Web Services Authentication Takes Leap Forward", Click here to be the first to post a talkback.


 
Scroll Up

   About | Term of Use | Privacy | Contact us | Tell a Friend | Advertise  

OSForge News RSS Feed