Operations // Identity & Access Management
2/19/2014
12:05 PM
Patrick Harding
Patrick Harding
Commentary
Connect Directly
Twitter
Google+
LinkedIn
RSS
E-Mail
50%
50%

'Connect': A Modern Approach To Mobile, Cloud Identity

A new protocol from the OpenID Foundation promises enterprises federated single sign-on that can scale.

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.

Both OAuth and Connect tuck into Web architectures and align with the Internet trend toward simple, light and functional (including standards such as Representational State Transfer (REST) and JavaScript Object Notation (JSON)) as opposed to heavy and highly architected standards. These developments not only align with app developers, but also administrators, who can avoid punching holes in firewalls by using simple REST calls associated with Connect.

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.

Patrick Harding is responsible for the Ping Identity product and technology strategy. He brings more than 20 years of software development, networking infrastructure, and information security to the role, which includes oversight of the Office of the CTO and Ping Labs. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
2/19/2014 | 5:04:47 PM
Security without passwords
Interesting approach, Patrick. I'm curious about how "Connect" squares with the efforts of the FIDO Alliance and its proposed new authentication standards for password-free computing. 
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio