After 9 months of hard work and sweat (not by me of course, but the Ping engineering, sqa and marketing teams), I’m proud to announce that we released our 3rd major product here at Ping — PingTrust v1.0. It’s the first complete stand-alone WS-Trust server and Security Token Service for creating, validating and exchanging security tokens. While at this stage it’s focused mostly on large, internal enterprise use-cases, it serves as the foundation for our support of Kim Cameron’s work around InfoCards and consumer facing identity. It’s basically a Java STS, which is the foundation for creating an InfoCards server in support of Microsoft’s identity metasystem.
Applications depend on user-level identity to protect critical resources, generate audit trails for regulatory compliance and support user-based billing. However, Web Services and SOA have lacked standards-based mechanisms for enabling trusted user identity, making these important functions difficult – if not impossible – without introducing proprietary application-level extensions that breach Web Services principles and introduce questionable security.
PingTrust builds on two open security standards that set the stage for true interoperability and a solution that scales. OASIS Web Services Security 1.0 (formerly WS-Security) allows for the embedding of security tokens in SOAP messages, while WS-Trust establishes a mechanism for obtaining and validating tokens from a Security Token Service (STS). PingTrust is such an STS. It supports both .NET and Java applications, Web-based and rich clients. PingTrust can operate on the Web Services Client-side, Provider-side or both sides of a Web Service transaction.
“With PingTrust, the concept of user session no longer ends at the application a user originally logs into, either directly or via federation,” commented Patrick Harding, chief technical officer, Ping Identity. “Instead, user session and identity now follow SOAP messages wherever they may go throughout the SOA.”
“By supporting WS-Trust, Ping Identity is providing a Security Token Service that can participate in the Identity Metasystem. This enables identity information to be exchanged using industry standard Web services, regardless of the underlying platforms” said Michael Stephenson, Director of Identity and Access at Microsoft. We look forward to Ping’s products interoperating with Microsoft technologies, including .NET, Active Directory and the upcoming ‘InfoCard’ technology.”
PingTrust: Caller ID for Web Services
Using PingTrust, a Web Services client can exchange the security token being used in the local security domain, such as a Kerberos ticket, for a SAML token that represents the original user’s identity in other federated security domains, including those at other companies. After being bound into a SOAP message and delivered to a Web Services Provider, the Provider will know who originated the request and will be able to use that information in determining how to process the request.
PingTrust is a lightweight, standalone, modular product that:
- Provides out-of-the-box support for several token types including SAML 1.1 and SAML 2.0, x.509, Kerberos and username/password, and is extensible to support custom tokens
- Provides a Web-based console for 100% GUI configuration
- Moves identity-related security and cryptography code out of applications by consolidating token security token processing into a centralized, shared server
- Aggregates trust management to dramatically simplify administration
- Does not require a heavyweight identity management system