Not just a Directory but a complete Directory Service Sun Directory Services

Wednesday Nov 04, 2009

Next week, Nov. 9-11, the Identity Management Team travels down to Gartner Identity Access Management conference to showcase two of our latest releases DSEE 7 and Role Manager 5.  Gartner IAM is a great event because it not only gather's together experienced practitioners in the identity management space but has a number of events that are small enough that you can have quality conversations about real problems.  Last year, Verizon presented at this conference on the Directory and OpenSSO implementation that serves 50M users.  The presentation is a great example of the proven expertise that Sun brings to Identity Management and the proven extranet scale our products can support---not a marketing benchmark.

publisherID=1460825906">

Our team has taken a different approach to this even this year and we are participating in Gartner's Learning Lab's.  Vendors, customer's and identity specialists are encouraged to come-by in a classroom style and learn about specific problem's Sun's product, partner's and customer's are doing to solve their identity business problems.  This is crucial today as the cost of failure or doing nothing rises exponentially.  The best way to ensure success is to learn from real-world implementations not marketing based slideware presentations.  This is why we have assembled not just the product teams but partners and real customer's to share their experience in these "learning labs".

The other great thing about Gartner IAM is that there are usually a few different ways to combine great industry expertise and a little fun.  On Tuesday, Nov. 10 at 9:00pm you can meet the Sun Identity team at the Hard Rock Rooftop bar for drinks and conversation.  The first 50 people get a wristband for free drinks.  Identity management isn't hard so come to the Hard Rock to find out how to make it easy! 

Gartner IAM Sun Schedule

Monday, Nov 9th

Learning Lab:

12:40 - 1:05pm “Increase Speed & Performance while reducing TCO with Sun Directory Server Enterprise Edition” Speaker: Nick Wooler, Sr Product Manager – Sun Microsystems

1:05 - 1:30pm “Changing the Rules of the game; Raising the bar with Rule Life-cycle Management and closed-loop remediation” Speaker: Neil Gandhi, Sr Product Manager – Sun Microsystems

1:35 - 2:00pm "IAM Governance, Risk and Compliance -- the future of IAM", Speaker: Sachin Nayyar, President - BrinQa

2:05 - 2:30pm "Enterprise Single Sign On for Sun Identity Management", Speaker: Stephane Fymat, VP of Strategy and Product Management - Passlogix

Sun Booth:

12:30 - 2:30pm Daniel Raskin showcasing OpenSSO

12:30 - 2:30pm Mat Hamlin showcasing Identity Manager

Tuesday, Nov 10th

Learning Lab:

12:10 - 12:35pm “Role based user provisioning; using business roles for identity life-cycle management and identity auditing”, Speaker: Mat Hamlin, Sr Product Manager, Sun Microsystems

12:35 - 1:00pm “Three tough challenges, one powerful solution: OpenSSO for web access management, federation and Web services security”, Speaker: Daniel Raskin, Chief Identity Strategist – Sun Microsystems

1:05 - 1:30pm "Privileged Identity Risk Management: Mitigating the Insider Threat", Speaker: Richard Weeks, VP of Channels and Business Development, Cyber-Ark

1:35 - 2:00pm "The WHO behind the WHAT: Arcot Authentication and Sun OpenSSO Enterprise "  Speaker: R 'Doc' Vaidhyanathan, Chief Product Officer - Arcot

Sun Booth:

12:00 - 2:00pm Nick Wooler, showcasing DSEE

12:00 - 2:00pm Neil Ghandi, showcasing Role Manager

Thursday Oct 22, 2009

Yesterday, Neil Ghandi, Matt Hamlin, Etienne Remillon and Nick Wooler gave a quick overview of what is new in Directory Server Enterprise Edition 7 and Role Manager 5.  Here are just a few of the great highlights that were discussed during the presentation.  Of course, you can get the full video embeded below.  Lastly, if you are interested in seeing more events like this you can go to the webinar site here.  

You can download the slides here.  You can download the video here.

Wednesday Feb 18, 2009

Daniel Raskin, Senior Product Line Manager for OpenSSO,  wrote a great blog today posting the slides and video recording of a recent presentation where Damodaram Bashyam, Directory of IT, at Verizon Wireless at Gartner IAM in Orlando last Fall.  The video below from Daniel's blog allows us all to hear about his deployment of OpenSSO and Directory Server.   It is an example of the great content that is presented at Gartner and we hope you will join us for the next Gartner conference in London on March 23-26.  

It is a powerful example of the talented engineers we have at Sun and the results of good partnerships with customers like Verizon.  Scalability and high availability are a part of our DNA at Sun and as you can see from the video and Damodaram's presentation we believe live case studies prove the value of our product better than any controlled benchmark.  Watch and listen:

Here is a quick overview of the performance statistics from the presentation.  Download it here

Thursday Dec 11, 2008

As President-elect Obama announced his Energy Team yesterday, I was excited for two reasons.  One, Steven Chu is a Californian from Lawrence Berkeley National Laboratory and it is nice to see local citizens playing National and Global roles improving our environment.  Two, I am proud to work at Sun because a large number of the energy innovators like Argonne Laboratory, which is also a part of the Department of Energy, are using Sun's Software to provide the backbone of innovation within these organizations.  

Argonne Laboratory uses Directory Server Enterprise Edition to power their collaboration infrastructure.  They also use MySQL, JavaES, OpenSSO Enterprise and Virtualization (e.g. xVM Server) to power their innovation.  You can see a great video with David Salbego, Director of IT Infrastructure at Argonne National Labs regarding his experience and business benefits resulting from Sun solutions. 

BC Hydro also used OpenSSO Enterprise and Directory Server to reduce cost of providing a web portal for their customers to get interact with their organization.  They reduced the use of paper and conserved resources for our environment.  You can read about the solution here.


Monday Jun 16, 2008

This document summarizes Sun support for Sun Java System products when used in conjunction with system virtualization products and features. 

http://docs.sun.com/source/820-4651/index.html

Directory Server Enterprise Edition is part of the Sun Java Identity Management Suite. Both the Native Package installation and Compress Archive installation versions of Directory Server Enterprise Edition are covered by this statement.

These statements are only valid for Directory Server Enterprise Edition 6.1 and above.


Monday Apr 28, 2008

Please see original security alert notification at http://sunsolve.sun.com/search/document.do?assetkey=1-66-235381-1

Document Audience:

PUBLIC
Document ID: 235381
Title: Security Vulnerability in Sun Java System Directory Proxy Server May Grant Unauthorized Administrative Access
Copyright Notice: Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved
Update Date: Fri Apr 25 00:00:00 MDT 2008

Solution Type Sun Alert

Solution  235381 :   Security Vulnerability in Sun Java System Directory Proxy Server May Grant Unauthorized Administrative Access  


Related Categories
  • Home>Content>Sun Alert Criteria Categories>Security
  •  
  • Home>Content>Sun Alert Release Phase>Resolved
  •  

Bug ID
6666615

Product
Sun Java System Directory Server 6.0, 6.1, 6.2, Enterprise Edition

Date of Resolved Release
25-Apr-2008

SA Document Body
Security Vulnerability in Sun Java System Directory Proxy Server 
May Grant Unauthorized Administrative Access

1. Impact

A security vulnerability in the Sun Java System Directory Proxy Server may allow a remote unprivileged user to gain unauthorized administrative access to the server. This is caused by the server incorrectly classifying a connection based on the "bind-dn" criteria, resulting in an incorrect policy being applied.

2. Contributing Factors

This issue can occur in the following releases for all platforms (Solaris 8, 9, and 10 SPARC and x86 Platforms, Linux, Windows, and HP-UX):
  • Directory Server Enterprise Edition 6.0, 6.1 and 6.2
Note: Directory Proxy Server 5.2 is not impacted by this issue.


To determine if the Directory Server running on a system is affected, the following command can be used:

$ dpadm -V

If the output contains the version string 6.0, 6.1 or 6.2, the system is affected by this issue.

3. Symptoms

There are no predictable symptoms that would indicate this issue has been exploited.

4. Workaround

There is no workaround for this issue. Please see the Resolution section below.

5. Resolution

This issue is addressed in the following releases:

DSEE 6.3 Native Package Versions:
  • Solaris 9 and 10 SPARC patch 125276-07 or later
  • Solaris 9 x86 patch 125277-07 or later   
  • Solaris 10 x86 and x64 patch 125278-07 or later
  • Linux patch 125309-07 or later
DSEE 6.3 PatchZIP (Compressed Archive) versions:
  • Solaris 9 and 10 SPARC patch 126748-04 or later
  • Solaris 9 x86 patch 126749-04 or later
  • Solaris 10 x86 and x64 patch 126750-04 or later
  • Linux patch 126751-04 or later
  • Windows patch 126753-04 or later
  • HP-UX patch 126752-04 or later
Note: The above patches can be installed on any impacted release to upgrade it to version 6.3, thereby resolving this issue.

For more information on the upgrade process please see the following:

Directory Server 6.3 Release Notes are available at:


and the Directory Server 6.3 Installation Guide is available at:


For more information on Security Sun Alerts, see Technical Instruction ID 213557.

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.


Attachments
This solution has no attachment

Thursday Apr 17, 2008

http://sunsolve.sun.com/search/document.do?assetkey=1-66-235361-1

Please see the above link for the official Sun Alert document.  The below information is provided for quick reference only.  

For additional details please also see previous blog entry on this topic: http://blogs.sun.com/dsee/entry/directory_server_6_2_database


Document Audience: PUBLIC
Document ID: 235361
Title: Sun Java System Directory Server 6.2 Database integrity may be compromised
Copyright Notice: Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved
Update Date: Mon Apr 14 00:00:00 MDT 2008

Solution Type Sun Alert
Solution  235361 :   Sun Java System Directory Server 6.2 Database integrity may be compromised

Bug ID: 6642430
Product: Sun Java System Directory Server 6.2, Enterprise Edition
Date of Resolved Release: 14-Apr-2008
SA Document Body: Sun Java System Directory Server 6.2 Database integrity may be compromised

1. Impact

A race condition may cause database pages for Sun Java System Directory Server to not sync to disk, resulting in possible Directory Server Database integrity issues. Depending on which pages are affected, the impact may vary.

2. Contributing Factors

This issue can occur in the following releases for all platforms (Solaris 8, 9, and 10 SPARC and x86 Platforms, Linux, Windows, HP-UX):
  • Sun Java System Directory Server Enterprise Edition 6.2
Note: Directory Server 6.1, 6.0, 5.2 and 5.1 are not affected by this issue.


To determine if the Directory Server running on a system is affected, the following command can be used:

$ dsadm -V

If the output contains the version string 6.2, the system is affected.

3. Symptoms

Depending on which database page is affected and which operation tries to access it, the resulting error messages can be different, but in the most frequent cases a message similar to the following is logged:

DEBUG - conn=-1 op=-1 msgId=-1 -  libdb: PANIC: fatal region error detected; run recovery

4. Workaround

There is no workaround for this issue. Please see the Resolution section below.

5. Resolution

This issue is addressed in the following releases: (please see blog entry http://blogs.sun.com/dsee/entry/dsee_6_3_released for more details)

DSEE 6.3 Native Package Versions:
  • Solaris 9 and 10 with SPARC patch 125276-07 or later
  • Solaris 9 x86 with patch 125277-07 or later
  • Solaris 10 x86 and x64 with patch 125278-07 or later
  • Linux with patch 125309-07 or later
  • Windows with patch 125311-07 or later
DSEE 6.3 PatchZIP (Compressed Archive) versions:
  • Solaris 9 and 10 with SPARC patch 126748-04 or later
  • Solaris 9 x86 with patch 126749-04 or later
  • Solaris 10 x86 and x64 with patch 126750-04 or later
  • Linux with patch 126751-04 or later
  • Windows with patch 126753-04 or later
  • HP-UX with patch 126752-04 or later
Note: After patches have been applied: Since the database integrity issue can be present but undetected, it is recommended to rebuild the database by exporting to an ldif file and reimporting the ldif file. In a replicated environment, all servers need to be rebuilt or reinitialized. Export/Import and initializing servers in a replicated environment is documented in the DSEE reference guide at:


This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.


Wednesday Apr 16, 2008

We have become aware of a bug in Directory Server 6.2 only that could cause database integrity issues.   We have a hotfix for this issue, and if you are running Directory Server 6.2 and run into this problem then you should contact Sun Support and ask for the fix for the following bug

6642430: DB corruption (zero’d pages) when performing db2ldif against large 20GB ldif file.

The sunsolve record for this bug can be found at http://sunsolve.sun.com/search/document.do?assetkey=1-1-6642430-1.

NOTE: This issue does not affect Directory Server 6.0 or 6.1 release so you only need this fix if you are running Directory Server 6.2.

After you have the hotfix for this issue on Directory Server 6.2 and have applied the hotfix, then you will have to re-initialize the database from an LDIF backup to fully correct the corruption issue. Simply applying the hotfix will not fix the database if the database is already corrupted. Database corruption can be present though not detected with data in binary formats. You must therefore rebuild the database by importing an LDIF backup.

Directory Server Enterprise Edition 6.2 is no longer available for download and Directory Server Enterprise Edition 6.3, which includes a fix for this issue, will be available for download early April.  When upgrading to Directory Server 6.3 from 6.2 (not needed if you are on 6.0 or 6.1), make sure you export the database (db2ldif) prior to the upgrade and then re-import the database after the upgrade to fully re-initialize the database and to ensure that no corruption issues remain.

Recommended patch or upgrade procedures:

  1. Shut down each directory server instance, as described in Starting, Stopping, and Restarting a Directory Server Instance.

  2. Perform an LDIF export of the database, as described in Backing Up to LDIF.

  3. Install the hotfix for bug 6642430 on Directory Server 6.2, or upgrade your Directory Server 6.2 instance to Directory Server 6.3 once Directory Server 6.3 is available for download (early April). You will need to login to Sunsolve in order to see this bug description.

  4. Re-initialize the database from the LDIF exported in step 2, as described in Importing Data From an LDIF File.

    If you are running replicated instances of Directory Server, make sure you read Restoring Replicated Suffixes as well.