Posts Tagged ‘SSO’

On the Road Again

Monday, November 10th, 2008

Just a quick announcement that our fearless leader Todd Clayton once again finds himself with a busy travel schedule over the next couple of weeks. For the next 3 days he’ll be attending the Gartner Identity and Access Management Summit in Orlando, FL. Or at least that’s what he tells us. After all, there’s another Orlando destination that could prove to be too tempting for Todd.

Next week, Todd will be attending CA World 08 at the Venetian Congress Center and Sands Expo in Las Vegas, NV from Monday 11/17 through Wednesday 11/19. Amazingly this will be Todd’s first trip to Vegas, so we highly encourage people to get him out and show him the sights. He was devestated to learn that Celine Dion is no longer doing her Vegas show, but we’ve assured him he’ll find other ways to enjoy his free time.

As always, we encourage you to connect with Todd if you’re planning to attend either of these events. Here’s a photo so you can pick him out in a crowd:

Todd on horseback

Todd in Colorado

(Just to be clear, he will not be on horseback at either event.)

Enterprise Microblogging Security

Tuesday, October 14th, 2008

Last week I read an article that was co-written by one of the most knowledgeable social media experts I follow on Twitter, Aaron Strout of Mzinga, and Joe Cascio of JoeCascio.net.  The article is titled Is the Enterprise Ready for Microblogging Tools Like Twitter?. It was full of useful information that any organization would want to consider before using a tool like Yammer or Present.ly, but the pieces that caught my eye were listed under the Key Considerations section:

“Single Sign-On (SSO): A growing problem in the social media world right now is identity proliferation. With some notable exceptions that accept OpenID, most sites still require you to create yet another account in their system (or identity domain). In most enterprises, a fair amount of effort has already been expended on establishing single sign-on through the intranets’ LDAP registry. It would be highly desirable to leverage this capability to enroll employees in the microblogging system. So, an enterprise microblogging solution must have flexibility in adapting to existing ID and sign-on registries.”

Then further down:

“Security: This will probably be of paramount concern at least initially in most businesses. Most corporations are very aware of keeping internal communications safe from prying outside eyes. An enterprise microblogging solution must provide for fine-grained authorization and trustworthy security of communications. Management, through the IT department will want to be able to restrict who can see certain posts.”

Some would say that the beauty of Twitter is its lack of walls. Granted you can globally secure your updates so that only those you approve may see them or leverage the DM feature to send private messages, but for the most part communication is done in the clear for all the Twitter community to see. But when discussions turn to private topics like corporate strategy and departmental policies, the need for enterprise microblogging to be secure becomes paramount. In other words, you don’t want that jab about a competitor’s product to become public because the person who made it was foolish enough to set their password = “password”.

So how secure are these new microblogging tools? A quick check of Yammer’s API Documentation shows the following:

“Authentication is done using HTTP Basic Authentication. The username is the full email address of the user, and the password is the same used to authenticate to the yammer.com web interface.”

It’s the same with Present.ly’s API Documentation:

“Just as with the Twitter API, the Present.ly API can be accessed via HTTP Basic authentication. The primary difference is that there is no data accessible without authentication in the Present.ly API, since the data is all private.”

For those who aren’t familiar with Basic Authentication, Wikipedia points out its main weakness:

“Although the scheme is easily implemented, it relies on the assumption that the connection between the client and server computers is secure and can be trusted. Specifically, the credentials are passed as plaintext and could be intercepted easily. The scheme also provides no protection for the information passed back from the server.”

This entry is not intended to knock Yammer or Present.ly for their API security protocols. I’m sure when their founders set out to deliver their solutions, security was barely a blip on their radars. But this is a security hole that Yammer & Present.ly’s customers will need to address if they want to provide secure microblogging environments for their employees.

If you’re part of an organization that needs help implementing SSO to a microblogging solution, or if you have any other security needs related to microblogging, we’d love to hear from you! CoreBlox has broad experience creating quick and effective solutions to these types of issues, and chances are we could help you figure this out. Drop us a line at info@coreblox.com, or feel free to contact me directly on Twitter.

For those folks who work in the Identity & Access Management space or just have a general interest in this area- what are your thoughts on the security challenges that these microblogging solutions pose? Anything you see that makes their situations unique relative to other applications that are covered by enterprise security?

Thank you, SiteMinder

Tuesday, August 19th, 2008

Seven years ago when I was working for Onyx Software, I led a CRM implementation for a Waltham, MA based company called Netegrity. Netegrity had made an early arrival to the Identity & Access Management (IAM) party, and its SiteMinder solution for single sign-on (SSO) had been wildly successful with Fortune 500 companies. About a year later when I was looking to reduce my travel load and get a view of the CRM world from the other side, I joined Netegrity’s Business Systems group where I began working with my fellow CoreBlox co-founders. Three years later CA acquired Netegrity, and shortly after that we launched CoreBlox.

Normally I would end that last paragraph with “And the rest is history…”, but it’s important to recognize a major component that has allowed our start-up to defy the odds and celebrate three years as a self-funded business: SiteMinder. There’s no doubt that having a strong, smart, versatile team has been a key to our success, but it would be difficult to pursue our Web 2.0 initiatives (such as our I Have Kids app which is up to 60,000 users!) if we were unable to find consistent sources of revenue to fund them. Our team’s SiteMinder expertise has allowed us to establish ourselves as a boutique firm in a niche market, and it has opened doors in other spaces such as directory virtualization and SAML/federation. In a down economy, IAM spending has remained strong enough to provide us with the engagements we need to drive our business forward:

… the number of organizations planning to roll out identity and access management solutions in the next 12 to 18 months increased 11 [percentage points], moving from 49 percent in 2006 to 60 percent in 2008.

As with any product or service that one works with on a daily basis, it’s easy to focus on gaps and frustrations. Sometimes we need to step back and recognize that what makes the solution complex leads to the opportunities that those who know it well can enjoy.

So on behalf of the entire CoreBlox team, I’d like to offer a sincere THANK YOU to SiteMinder. May you continue to send great opportunities and clients our way!

Single Sign-On and Virtual Directories: A Match Made in Heaven

Friday, May 9th, 2008

Single sign-on (SSO) alone is not enough to deliver a unified customer experience. This becomes more apparent as companies attempt to implement cross application SSO for disparate sets of users. SSO falls short as companies expand beyond a defined set of internal-only users into cross business unit applications and especially for applications geared towards external users. While SSO tools allow companies to interweave applications running on disparate platforms into complex mashups presenting a unified view of information, they often lack the mechanism to relate users across the systems. Enter the virtual directory server. By combining the power of SSO with the abilities of a virtual directory server to correlate user information based upon complex matching rules, companies gain a unique ability to easily bring together applications while reducing integration costs and time to market.

The concept dubbed “Identity Acquisition” exemplifies these benefits. In essence, this is the ability for companies to quickly subsume applications and users into a broader infrastructure that allows easy presentation of a unified appearance and linking of application functions. Through the use of a virtual directory, companies can create a unified view of a user across all of their applications and leverage that information to present a single set of security roles to SSO applications. This allows SSO products to pass the correct identity to the underlying application regardless of the differences in user directories and attributes. Without a mechanism for identifying these users in a composite view, SSO provides superficial benefits lacking the ability to deliver a common experience as a user moves across these disparate applications. Just because a user may be xyz@company.com in one application, they could be identified as id=130203 in another. Although SSO can grant the user access to both applications, without a correlation established and a way to leverage that correlation to create a unified profile, the ability to deliver a common experience to that user across both systems is lost.

Typically companies have a set of key objectives when looking to deliver a common user experience. These may include the ability to:

  • Efficiently roll-in newly identified applications
  • Integrate multiple user bases into a common delivery platform and exploit the “up-sell” factor.
  • Expedite the integration of newly acquired identities and applications to reduce confusion and increase satisfaction
  • Create a repeatable process with known costs and timelines
  • Reduce security concerns and increase compliance of managing multiple identifies and non-centralized application policies

A combined SSO and virtual directory infrastructure enables companies to meet these requirements and to provide an agile platform for changes in business objectives and processes.

How to Put the Pieces Together

The key to laying this foundation is to create a technology stack that includes a flexible set of tools that allows for easy acquisition of identities into a common platform. Recently, we were faced with the challenge of assisting a company that was making multiple acquisitions. They needed to continue to give their customers a common view of technical support during the assimilation period of the acquired systems into the broader application environment. Upon closer examination of the support tools currently in use the company discovered that they:

  • Needed to increase customer satisfaction
  • Needed to drive down technical support costs
  • Found too few customers utilizing self-help options (approximately 20%)
  • Were losing revenue due to a lack of ability to perform entitlement checking
  • Had too many environments to effectively manage and no centralized control
  • Found it difficult to support customers who had products from different business units because they were supported by different systems
  • Had increasing demands upon limited resources such as legacy applications

One of the key goals of the project was to entice customers to use self-help options. The objectives included:

  • Single Sign-on, for customers to login only once
  • Global Search, so that customers could search view content-rich knowledgebase content across all support systems
  • Unified issue resolution capabilities across business units
  • A new base security architecture to accommodate future expansion

The overall solution was made up of the following components:

  • RadiantLogic RadiantOne Virtual Directory

Consolidates and caches user profiles (including all necessary attributes) from all user repositories into a single LDAP source, enabling the Policy Server to authenticate and authorize users against a single directory

  • CA SiteMinder

Enables enterprise security and single sign-on capabilities across all application platforms

  • SAP Portal

Allows a single front-end presentation layer across all legacy systems

  • IBM WCDS/OmniFind

Unified 3rd-generation knowledgebase across all acquired systems

  • CA eTrust Directory/MS SQL/Sybase/MySQL/ADAM

Backend application user stores containing the various disparate identities specific to that application

The following diagram highlights the solution landscape:

Solution Overview

Each of these components allowed the company to establish a base platform for current requirements while also creating capacity for future acquisitions. RadiantOne played a key role by providing to SiteMinder a central location for user authentication and authorization through virtualizing multiple instances of the same user distributed across all systems, into a single global profile.

Measurable Results

The new system greatly increased the company’s ability to meet the desired goals. The platform ensured that:

  • All external technical support systems are available through a single login and through single sign-on
  • They are able to present unified entitlements and system access for customers owning multiple products
  • Customer have the ability to search across all content regardless of differences in physical location of the data, improving self-service
  • The enhancements to the identity security infrastructure reduced costs

The effort yielded an increase both in customer and employee satisfaction as well as a significant reduction in the time required to make system changes. This combination of SSO and virtual directory technology delivered a match made not only in heaven, but also right here in our data centers.