Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 939539642 for ; Tue, 21 May 2013 22:42:20 +0000 (UTC) Received: (qmail 43648 invoked by uid 500); 21 May 2013 22:42:20 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 43597 invoked by uid 500); 21 May 2013 22:42:20 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 43589 invoked by uid 99); 21 May 2013 22:42:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 22:42:20 +0000 Date: Tue, 21 May 2013 22:42:20 +0000 (UTC) From: "Bob Hehmann (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DIRSERVER-1816) Unable to enable SSL to the APACHE DS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSERVER-1816?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 13663515#comment-13663515 ]=20 Bob Hehmann commented on DIRSERVER-1816: ---------------------------------------- Emmanuel, thanks for the quick response. I didn't realize the correct bound= ary between DS and Studio within JIRA - I got to the original bug report se= arching for the specific error codes presented to me, which indicated the e= xact same bug in DS itself, M11 I believe. That reporter was directly editi= ng the LDIF files, while I was coming in through Studio. When I read that b= ug, I thought the same fundamental error was in play, likely common code, w= ith the same possible work-around for what appeared to me an as yet unresol= ved problem. I do agree I shouldn't have been whining publically - a poorly thought-thro= ugh reaction on my part to hitting my second show-stopper in 2 hours, havin= g started with the latest (I believe) GA versions of both DS and Studio. My= job and time demands preclude me providing much tangible help. But I would= communicate a QA process concern, triggered by my encountering a fatal fai= lure in step 2 of the most basic installation process (rather than in far m= ore obscure and difficult to test situations.) After installing Studio (GA)= : Step 1 - establish a connection within Studio to the DS - OK; Step -2 ope= n the DS Configuration from within Studio - hard fail, due to DS M12 and St= udio M6 being incompatible in their naming of fundamental and mandatory dir= ectory attributes. The answer to that bug report (DIRSTUDIO-864) dating fro= m January, and apparently recurring, is that DS attributes are being rename= d, and Studio apparently isn't being kept reliably synchronized - in GA rel= eases. That's the bug that moved me to a latest daily build variant of Stud= io (798), and off of the GA release, so I could use Studio at all. Perhaps = the basic QA test scripts behind a GA release are missing some remedial ste= ps. Regardless, its back to salt mining - no rest for the wicked.... Cheers, Bob Hehmann Solutions Architect || Healthcare & Services, Wipro Infocrossing || 6320 Ca= noga Ave., Woodland Hills, CA 91367 Suite 600 || P: 714.986.8731 || F: 714.= 986.8776 || C: 805.906.0492 || bob.hehmann@wipro.com **Think=C2=A0Green =C2= =A0- Please print responsibly** =20 > Unable to enable SSL to the APACHE DS=20 > -------------------------------------- > > Key: DIRSERVER-1816 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1816 > Project: Directory ApacheDS > Issue Type: Task > Components: ldap > Affects Versions: 2.0.0-M10 > Environment: Windows=20 > Reporter: RakeshAcharya > Priority: Blocker > Labels: security > Original Estimate: 24h > Remaining Estimate: 24h > > Below are steps taken to enable SSL > 1. Created a new valid Key pair using Portecle. > 2. Placed the KeyStore in the conf directory=20 > 3. Added the below entry in the conf.ldif file > ads-ldapServerCertificatePassword > ads-ldapServerKeystoreFile > also tried below entries > keystoreFile ,certificatePassword=20 > ads-ldapServerKeystoreFile,ads-ldapServerCertificatePassword > Facing below error while starting the server > Error: > ERR_04447_CANNOT_NORMALIZE_VALUE Cannot normalize the wrapped value ERR_0= 4473_NOT_VALID_VALUE Not a valid value 'C:\Users\rakeshacharya\.ApacheDirec= toryStudio\.metadata\.plugins\org.apache.directory.studio.ldapservers\serve= rs\f9ed386b-f8a9-4a79-be12-b5cfabf362be\conf\localhost.jks' for the Attribu= teType 'ATTRIBUTE_TYPE ( 1.3.6.1.4.1.18060.0.4.1.2.308 > NAME 'ads-keystoreFile' > DESC The keystore file to use to store certificates > EQUALITY caseExactMatch > ORDERING caseExactOrderingMatch > SUBSTR caseExactSubstringsMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 > SINGLE-VALUE > USAGE userApplications > ERR_04269 ATTRIBUTE_TYPE for OID certificatepassword does not exist -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira