Return-Path: X-Original-To: apmail-archiva-users-archive@www.apache.org Delivered-To: apmail-archiva-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 973AC7455 for ; Sun, 13 Nov 2011 21:14:34 +0000 (UTC) Received: (qmail 4358 invoked by uid 500); 13 Nov 2011 21:14:34 -0000 Delivered-To: apmail-archiva-users-archive@archiva.apache.org Received: (qmail 4320 invoked by uid 500); 13 Nov 2011 21:14:34 -0000 Mailing-List: contact users-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@archiva.apache.org Delivered-To: mailing list users@archiva.apache.org Received: (qmail 4312 invoked by uid 99); 13 Nov 2011 21:14:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Nov 2011 21:14:34 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.160.170] (HELO mail-gy0-f170.google.com) (209.85.160.170) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Nov 2011 21:14:27 +0000 Received: by gyg13 with SMTP id 13so4433096gyg.15 for ; Sun, 13 Nov 2011 13:14:03 -0800 (PST) Received: by 10.68.34.199 with SMTP id b7mr33458044pbj.105.1321218842870; Sun, 13 Nov 2011 13:14:02 -0800 (PST) Received: from [192.168.0.102] (rrcs-76-79-84-246.west.biz.rr.com. [76.79.84.246]) by mx.google.com with ESMTPS id n4sm36568984pbo.10.2011.11.13.13.14.01 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 13:14:02 -0800 (PST) Sender: Brett Porter Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1251.1) Subject: Re: Weird problems with LDAP integration From: Brett Porter In-Reply-To: <32834029.post@talk.nabble.com> Date: Sun, 13 Nov 2011 13:13:57 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <1D70238A-8692-4A28-BC86-65B683811756@apache.org> References: <32834029.post@talk.nabble.com> To: users@archiva.apache.org X-Mailer: Apple Mail (2.1251.1) X-Virus-Checked: Checked by ClamAV on apache.org Make sure you have configured an admin user that exists in LDAP - at the = moment there's no way to use an internal user for that. Here is a configuration template I use which should show the values = you'd need to populate: = https://github.com/maestrodev/puppet-archiva/blob/master/templates/securit= y.properties.erb On 12/11/2011, at 11:21 PM, sam-the-man wrote: >=20 > I'm coming to the end of a long, drawn-out server setup. >=20 > Archiva is the last piece of the puzzle. The kicker - I need to get it = to > authenticate and authorize using ldap. >=20 > I know my LDAP server is working fine. Archiva is (was?) working fine = too. >=20 > So I install archiva and load it for the first time. It forces me to = create > an admin. Then I'm in, it works, etc. >=20 > So I add all the LDAP configuration options to the security.properties = file, > and then restart archiva. >=20 > When the LDAP stuff is in the security.properties file, and I try to = access > archiva, it goes back to the create admin field no MATTER what I do, = or what > I click. I already created an admin, so why is it trying to force me = to make > another after I add the LDAP stuff? Configuration files coming... >=20 >=20 > --=20 > View this message in context: = http://old.nabble.com/Weird-problems-with-LDAP-integration-tp32834029p3283= 4029.html > Sent from the archiva-users mailing list archive at Nabble.com. >=20 -- Brett Porter brett@apache.org http://brettporter.wordpress.com/