Return-Path: X-Original-To: apmail-manifoldcf-user-archive@www.apache.org Delivered-To: apmail-manifoldcf-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD4C4F79E for ; Tue, 6 Aug 2013 08:12:03 +0000 (UTC) Received: (qmail 44614 invoked by uid 500); 6 Aug 2013 08:12:01 -0000 Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org Received: (qmail 44278 invoked by uid 500); 6 Aug 2013 08:11:51 -0000 Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@manifoldcf.apache.org Delivered-To: mailing list user@manifoldcf.apache.org Received: (qmail 44247 invoked by uid 99); 6 Aug 2013 08:11:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 08:11:48 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [67.192.241.171] (HELO smtp171.dfw.emailsrvr.com) (67.192.241.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 08:11:39 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp17.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 150CE1882E6 for ; Tue, 6 Aug 2013 04:10:58 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp17.relay.dfw1a.emailsrvr.com (Authenticated sender: msheppard-AT-funnelback.com) with ESMTPSA id D8BE5188373 for ; Tue, 6 Aug 2013 04:10:57 -0400 (EDT) Received: by mail-vb0-f54.google.com with SMTP id q14so67084vbe.27 for ; Tue, 06 Aug 2013 01:10:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=egBfJu1Jp/n/zocLvpxGZ3sFpQcJWLdTDiKZAS8CK4g=; b=KffMzZfqfL6HZFfSk98u+/dCuO1zLa67Yveg6vqS/dQzo6XNG1BY+5Q+PPTEbRx+Rs I5ieJYVo1xFuccnxC3BT5MD9ItNmimMcHRW1dYOuF35L1Wj1KyrBwEAG3+pv4OrrBtKM UK2VTFayalOFaU7/4NZO7urbjHZ4ALNuqmbOgd/H/v2F2xqMiShIpNvSQ6wEkiTw7TNj QB7IaX7Qy5/MdlJBa0aeKgicWdG8Eq+OqNkm8ib+P8xFBJ+ZsCuIYaVQGizoIHFeGN5A QRvFFzG6KBisOY8m6FrNgTHYoMvTYL4dz03PNflLTiPtPoa9BHYQ4sALE1gcSsl5zwYw cA2w== X-Gm-Message-State: ALoCoQlIoIWv6UXgVPDJgl2N2x0bYLZUZF7xyw08vD2mogi4SB9OAdM3Aptjo+YxfDXOhpJ30Ovu MIME-Version: 1.0 X-Received: by 10.58.6.210 with SMTP id d18mr3272vea.96.1375776657403; Tue, 06 Aug 2013 01:10:57 -0700 (PDT) Received: by 10.220.168.143 with HTTP; Tue, 6 Aug 2013 01:10:57 -0700 (PDT) X-Originating-IP: [103.15.168.1] Date: Tue, 6 Aug 2013 18:10:57 +1000 Message-ID: Subject: Disabling login on ManifoldCF 1.3 From: Matthew Sheppard To: user@manifoldcf.apache.org Content-Type: multipart/alternative; boundary=047d7b6d84e8f487cc04e342f674 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b6d84e8f487cc04e342f674 Content-Type: text/plain; charset=ISO-8859-1 I'd like to disable the new login for the ManifoldCF interface - Is this possible, and if so how? --- Background ---- I currently have a copy of ManifoldCF included along with another application, and our setup arranges for our app server to authenticate users before they reach the ManifoldCF interface (mcf-combined-service.war). Since upgrading to 1.3 I see an additional login page (login.jsp) which appears after our login process completes. It looks like this new login page uses a username and password set via the org.apache.manifoldcf.login.name and org.apache.manifoldcf.login.password properties ( http://manifoldcf.apache.org/release/trunk/en_US/how-to-build-and-deploy.html ). Since the double login and different username/password setup is likely to be confusing to our users, and since the new ManifoldCF system does not seem to allow us to use the same credentials as are used for the rest of our system easily, I'd like to turn off the ManifoldCF login leaving only our app server one. Looking briefly around I can't see any setting to disable the new login, but hopefully I'm missing something. ---- ---- Many thanks for any assistance anyone can provide, Matt Sheppard --047d7b6d84e8f487cc04e342f674 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I'd like to disable the new login for the Ma= nifoldCF interface - Is this possible, and if so how?

--- Background ----

I currently have a copy of Ma= nifoldCF included along with another application, and our setup arranges fo= r our app server to authenticate users before they reach the ManifoldCF int= erface (mcf-combined-service.war).

Since upgrading to 1.3 I see an additional login page (login.jsp)= which appears after our login process completes. It looks like this new lo= gin page uses a username and password set via the org.apache.manifoldcf.login.name and org.apa= che.manifoldcf.login.password properties (http://manifoldcf.= apache.org/release/trunk/en_US/how-to-build-and-deploy.html).

Since the double login and different username/password setup= is likely to be confusing to our users, and since the new ManifoldCF syste= m does not seem to allow us to use the same credentials as are used for the= rest of our system easily, I'd like to turn off the ManifoldCF login l= eaving only our app server one.

Looking briefly around I can't see any setting to disabl= e the new login, but hopefully I'm missing something.
---- ----
<= br>
Many thanks for any assistance anyone can provide,
Matt Sh= eppard
--047d7b6d84e8f487cc04e342f674--