Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Speaking SAML: Page 2 of 5

Authorization assertions permit or deny access to specific resources--a file, device, Web page, specific database field or actions, like updating a list of phone numbers. The trade-off of, say, micromanaging access down to the field level of a database, of course, is that you have to develop and maintain a large security policy. But given recent regulations such as HIPAA (Health Insurance Portability and Accountability Act) and the Gramm-Leach-Bliley Act, this kind of detailed security management is a necessity in the financial, health-care and insurance industries.

SAML attribute assertions let you authorize users to access certain information in an application based on their "VIP-Status" or "Member_Level." (For more on assertions, see "The Three As").

SAML protocols define the format of requests and responses. All SAML exchanges, for instance, assume a trust relationship between the requestor--the application being requested--and the responder. Both parties must reference the same subject, so there's only one subject named "Bruce," for example, in the SecurityDomain "nwcinc.com."

Each request and response has a common header and is defined in a SAML document with the name space samlp. All SAML assertions are prefixed with the namespace saml, and each of the three types of assertions has a corresponding request protocol (see "Request and Response" at left).

Aside from the basic protocols, SAML also defines artifacts for browser redirection and single sign-on. An artifact is a pointer to a SAML assertion so that the application or Web server can retrieve the assertion. An artifact is small--less than 64 KB.

Bindings and Profiles