I don't need to tell anyone about the problems with passwords. The focus should be on looking forward to a development coming next week that provides the best shot yet to improve security in growing mobile and social environments.
It's called OpenID Connect. It's a protocol, and it should be on enterprise radar screens as an authentication building block for SaaS, mobile apps, and other resources, available via a multitude of devices that are currently suffering from a lack of credible access controls.
Infrastructure isn't sexy, but when not done right it can contribute to issues that are downright scary, such as millions of passwords and accounts stolen last year from retailers and service providers far and wide.
Connect has been described as “the DHCP for identity” because it promises scalable single sign-on at a time when connections are crisscrossing among companies, service providers, and business partners. It’s technology that is coming around the corner and promises to bring options to enterprise users looking for federated single sign-on at scale for mobile and cloud environments
OpenID Connect v. OpenID 2.0
The protocol forms part of a modern architecture for identity and access management to support mobile, cloud and API-integration scenarios.
Connect is not the OpenID 2.0 protocol that many in the industry have discounted over the years. In fact, Connect erases the sins and deficiencies of the past. The protocol is a simple identity layer built on top of the Internet Engineering Task Force standard OAuth 2.0. From a very high level, OAuth is about granting access, while Connect is about authentication. Simply put, Connect provides the pattern for how to securely pass identity information.
In addition, Connect provides a single security protocol for both B2C and B2B environments, and offers multiple grades of authentication. The protocol is API-friendly and adapts to native and mobile applications. It supports robust signing and encryption. Now that approval is imminent, I expect it to be an important building block in access control strategies going forward.
Enterprise building block
Enterprises are acutely aware that they need to address new security concerns in distributed architectures that feature cloud services, transparent security boundaries, and untethered, device-crazy end-users.
Connect will aid in reducing the number of sign-on credentials end-users must remember to a few secure accounts that are maintained by trusted identity providers -- including the enterprise. And it can be used by any number of clients for authentication to resources.
The spec confines complexity to a single place and enables a consistent, secure, predictable experience that improves chances of detecting fraudulent use of identity. It has been in development for the past four years, and has been tested in production environments at Salesforce, Google, Microsoft, Yahoo, and many others.
The OpenID Foundation, which has fostered development of the standard, also has developed a common user interface, called Account Chooser, aimed at standardizing sign-on procedures to reduce end-user confusion.
It's true that no one buys protocols, but Connect is shaping up to be one important building block and an area for enterprises to explore.