research center:

Applications

Home

Applications Convergence / VoIP LANs / Routers Network Management Network Storage Operating Systems Security Servers / Data Center Small / Med. Business Wide Area Network Wireless / Mobile

News Events Buyer's Guides

Vendor Solutions

White Papers Special Reports Webcasts Partner Sites -Secure Routing -ProCurve Networking -Enterprise Security -Software Dimension -Application Acceleration -IT Agility -Networking Solutions

Site Resources

Product Tests Buyer's Guides NEW Video Library Demo.com Careers Newsletters This Week in Print Opinions Blogs Podcasts Encyclopedia Forums RSS Feeds Special Issues Network Life

About Us NW Subscription

Special Issues

Signature Series
Enterprise All-Stars NEW

You in action

New Data Center
Wireless & Mobility NEW

Server Virtualization

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

NetworkWorld.com > Resource Links: Encyclopedia: S

SAML (Security Assertion Markup Language)

SAML defines XML/Simple Object Access Protocol-based protocol interactions that support real-time authentication and authorization across federated Web services environments. The standard defines request and response messages that security domains use to exchange authentication, attribute and authorization information in the form of trust-assertion messages about named users and resources. Users log on to their home domains through authentication techniques such as ID/password or Kerberos, and this authentication is communicated to a federated destination site through a SAML authentication assertion.

From Federation key to Web services, Network World, 04/29/02.

End user's browser accesses authentication server, and authentication server asks for user ID and password. End user requests a resource from destination/Web services server. Authentication server opens a session with destination server.

End user enters ID and password. Authentication server checks with LDAP directory and then authenticates end user. Authentication server sends uniform resource identifier (URI) to end user. End user browser is redirected to URI, which connects end user to Web service.