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
Newest First  |  Oldest 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
Cartoon
Current Issue
Dark Reading, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0993
Published: 2014-09-15
Buffer overflow in the Vcl.Graphics.TPicture.Bitmap implementation in the Visual Component Library (VCL) in Embarcadero Delphi XE6 20.0.15596.9843 and C++ Builder XE6 20.0.15596.9843 allows remote attackers to execute arbitrary code via a crafted BMP file.

CVE-2014-2375
Published: 2014-09-15
Ecava IntegraXor SCADA Server Stable 4.1.4360 and earlier and Beta 4.1.4392 and earlier allows remote attackers to read or write to arbitrary files, and obtain sensitive information or cause a denial of service (disk consumption), via the CSV export feature.

CVE-2014-2376
Published: 2014-09-15
SQL injection vulnerability in Ecava IntegraXor SCADA Server Stable 4.1.4360 and earlier and Beta 4.1.4392 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

CVE-2014-2377
Published: 2014-09-15
Ecava IntegraXor SCADA Server Stable 4.1.4360 and earlier and Beta 4.1.4392 and earlier allows remote attackers to discover full pathnames via an application tag.

CVE-2014-3077
Published: 2014-09-15
IBM SONAS and System Storage Storwize V7000 Unified (aka V7000U) 1.3.x and 1.4.x before 1.4.3.4 store the chkauth password in the audit log, which allows local users to obtain sensitive information by reading this log file.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
CISO Insider: An Interview with James Christiansen, Vice President, Information Risk Management, Office of the CISO, Accuvant