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. 
Printers: The Weak Link in Enterprise Security
Kelly Sheridan, Associate Editor, Dark Reading,  10/16/2017
20 Questions to Ask Yourself before Giving a Security Conference Talk
Joshua Goldfarb, Co-founder & Chief Product Officer, IDDRA,  10/16/2017
Why Security Leaders Can't Afford to Be Just 'Left-Brained'
Bill Bradley, SVP, Cyber Engineering and Technical Services, CenturyLink,  10/17/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.