Intel announced Intel® Expressway Cloud Access 360 at Cloud Connect. This software provides cloud account provisioning, federated single sign-on into software as a service, two-factor authentication using one-time password soft tokens and context-based access control leveraging Intel® Identity Protection Technology clients. Cloud connectivity for applications and data is delivered through SAML, OAuth, OpenID and XACML standards.
Welcome to SAML XML.org.
This is the official community gathering place and information resource for the SAML OASIS Standard. SAML provides an XML-based framework for creating and exchanging security information between online partners. This is a community-driven site, and the public is encouraged to contribute content.
Trusted Client-to-Cloud Access with Intel
Okta Publishes Okta Scale to Accelerate Secure Adoption of Enterprise Cloud
Okta has published a rating system for companies adopting SaaS applications, as well as guidance to help developers create more secure and manageable solutions for their customers. The Okta Scale rates each SaaS application based on its ability to meet enterprise identity management requirements and gives enterprise IT teams a way to better gauge the overall manageability of cloud applications...
SecureAuth wins Info Security Products Guide awards
SecureAuth Corporation announced today that Info Security Products Guide has named SecureAuth IEP a winner of the 2011 Tomorrow's Technology Today Award in two categories. The SecureAuth Identity Enforcement Platform (IEP) was selected based on technologies that are making the most positive impact on security in today's highly sophisticated and blended attacks environment.
PhoneFactor supporting SAML 2.0
PhoneFactor announced support for SAML 2.0, a standard for communicating identity information in the cloud. By providing support for SAML, PhoneFactor enables federated two-factor authentication for Google Apps, SalesForce.com, and other cloud services and platforms.
authnrequest invalid signature
i receive a 'invalid signature' from the IDP (</samlp:StatusCode>), what causes this message to appear? what part of the authnrequest should be signed? and how does the idp validate it? i dont understand how it is possible that the element with the signature is within the element that needs to be signed (root?) (if that is the case)

