Enterprise Positioning

THE ENTERPRISE CHALLENGE
Enterprises need a holistic IDM strategy, process and tool, that effectively interfaces identity across a diverse set of communities and domains:


 * Allow the user be reliably identified
 * User can use an identity they already have created anywhere
 * Use this to provide a personalized service to a broader audience


 * High barrier of entry for certain low sensitivity applications


 * Time and cost for integrating M&A

IDM 1.0:
Reducing cost of managing fragmented identities while retaining high level of trust:
 * Evolving from identity application silos to a reduced SSO for the enterprise
 * Cost Reduction
 * Federation for trusted enterprises

IDM 2.0:

 * User Centric approach to Identity Management: User’s creating and maintaining identity and claims (i.e., the “IP of identity”)
 * User Control: Choosing which identity credentials to present in response to an authenticating or attribute request
 * User Consent: User can always control or deny whether info about them is released
 * IDM 2.0 provides functionality capabilities not in IDM 1.0 – not a superset of federation

What are the typical goals of Enterprise IDM 2.0?

 * Extending Reach
 * Lower Cost
 * Lower Barriers of Entry


 * Strong driver to extend reach to communities to generate additional revenue and reduce costs & by selling products & services and eliminating the barrier for registration and identity.
 * 1) A horizontal identity management solution that allows identity to be effectively interfaced &  portable across domains and communities
 * 2) Allow users to create and maintain identity:  Make it easy for customer to interact with  web 2.0 communities and beyond
 * 3) Lightweight identity solution that reduces barriers of entry to other communities, but also within HP
 * Provide a low barrier of entry for certain low sensitivity applications
 * Provide a quicker and secure identity management solution for M&A

Enterprise Customer IdM 2.0
The challenge: extending reach beyond the captive domain into new and diverse communities

Known                Less-known             Unknown <->

Captive              Cultivated             External Users                Communities

<-> Customers            Communities            External Partners                Blogs               Communities

What are the IDM themes around extending global reach?

 * Overall strategy is to market products and services to communities beyond the current captive domain
 * Allow the user be reliably identified
 * User can use an identity they already have created anywhere
 * Use this to provide a personalized service to a broader audience
 * Make it easy for customer to interact with enterprise communities and beyond
 * Provide a low barrier of entry for certain low sensitivity applications
 * Provide a quicker and secure identity management solution for M&A

Lightweight Idm solution

 * Provide a lightweight identity architecture approach that is simpler, cheaper and faster for integration.
 * Reduces barriers of entry for M&A
 * Added on – but does not replace core HP IDM 1.0 capabilities
 * May mask some levels of back end fragmentation
 * Trust for highly sensitive content is an issues
 * The model of an enterprise being its own RP and masking OpenID needs to be considered

Cultivated and External Communities

 * External to your captive community - these communities represent to a significant opportunity to increase your global reach
 * Communities that are for shared interest represents community thought leadership that goes beyond an individual
 * Typically a minimal set of information exits that user’s claim
 * Bridging identity into these domains removes key barriers of entry:
 * Registration abandonment
 * ID fatigue among users
 * Expensive to maintain a shared IdM (e.g. federation) infrastructure for these types of users

Calls
02/06 - 2:00 to 3:00 PST - Meet # 866-401-6110 Session ID 857 6924

Hello Folks, This is the date for our next working meeting Actions from our 01/23 meeting
 * 1) Kaliya reviewed process for charter approval and working group structure - complete
 * 2) Discuss need for article on workgroup for IDCommons news letter - Pete submitted draft to Kaliya and Gary
 * 3) Review drivers / framing document from previous discussion - complete
 * 4) Create a summary spreadsheet of use cases / drivers to be addressed and team provide input - Gary
 * 5) Schedule next working session. - complete
 * 6) Did I miss anything?

Actions from our 01/09 meeting:
 * 1) Gary, Pete and Kaliya to update charter document - Complete
 * 2) Team review document post updates and provide feedback - Complete
 * 3) Gary to schedule charter review / approval - Complete charter submitted
 * 4) Meet again next week to start defining content / deliverables.

NOtes for Call on Jan 23.

Themes: Extending the Enterprise


 * 'captive users' - self registred, verified
 * 'cultivated community' trying to get customers to interact (need consistant strategies)
 * 'external' larger internet world as a whole - opportunities - no way to know about or interact directly.

Thrust around OpenID - trying to tap into cultivated and external communities. Move up through levels of membership. They represent huge marketing capability.

Problem with global identity management with customers - they are centralized. VPN managed globally - administrative domains of identity are local in geography - in part data privacy. Managing across this spectrum of domains. Technologies being developed in User-centric community that can be used to address these business problems.

Idea: Messaging similar to the way design patterns are used. in the sense that we are talking about for people. We can describe things in this way. Yeah- I got that problem. matches context so what do I do. Look at Slides - consistent across all domains.

Cost effective - Light weight identity management.