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 8A6221055A for ; Sat, 9 Nov 2013 02:25:17 +0000 (UTC) Received: (qmail 38319 invoked by uid 500); 9 Nov 2013 02:25:17 -0000 Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org Received: (qmail 38283 invoked by uid 500); 9 Nov 2013 02:25:17 -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 38273 invoked by uid 99); 9 Nov 2013 02:25:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Nov 2013 02:25:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mlibucha@gmail.com designates 209.85.220.177 as permitted sender) Received: from [209.85.220.177] (HELO mail-vc0-f177.google.com) (209.85.220.177) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Nov 2013 02:25:11 +0000 Received: by mail-vc0-f177.google.com with SMTP id ib11so1923373vcb.36 for ; Fri, 08 Nov 2013 18:24:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=fv0kfhEnMogPWI+CL1CWdp5Wq9xjU+PkULYkv5ZkDIU=; b=TrJ4YPGR4i/FfEOCDCQtVfHw9DVN6n0jHOgKbE5EUe+TdCsovV9TPnvdncrQUqvwUX KnVUgZ00eb7i3JU4KOAKL8069+vixnFLYZvvQCuLjSIH5S8X6zL2GNng0OgLe27HSd8f HoSxDOuXnYurg/IVsLa9R1wvVQ7sBwgQeWuvLVZMI6Rqw5C4xmra0YeYic4zS5nUBpQq a64+26I7SDRZaJbJSvVtPbWm+GXxtmmoNxu1tVdI643azXGGCyittz3aUg1zPR32oEN0 PmUP5WJAvkMA30HutqNE+AHkSURjUJWkAobrsiZGYxYiGuHgRFYHn9iDOMmPxpX6gylA rOMQ== MIME-Version: 1.0 X-Received: by 10.220.49.8 with SMTP id t8mr48289vcf.49.1383963890128; Fri, 08 Nov 2013 18:24:50 -0800 (PST) Received: by 10.58.235.36 with HTTP; Fri, 8 Nov 2013 18:24:50 -0800 (PST) In-Reply-To: References: Date: Fri, 8 Nov 2013 18:24:50 -0800 Message-ID: Subject: Re: Authority Service questions From: Mark Libucha To: "user@manifoldcf.apache.org" Content-Type: multipart/alternative; boundary=089e0163420e0da09e04eab534a5 X-Virus-Checked: Checked by ClamAV on apache.org --089e0163420e0da09e04eab534a5 Content-Type: text/plain; charset=ISO-8859-1 Thanks, Benjamin. Yes, that works. Much appreciated. Mark On Fri, Nov 8, 2013 at 4:24 PM, Benjamin Brandmeier wrote: > Evening Mark, > > you need to define authority connections. > By calling the authority service with a given username (+domain) the > defined source systems will be queried for the currently existing tokens > (e.g. ACL-IDs). This happens every time a query is performed (Caching not > counted). > > Please correct me if I'm wrong. > > Benjamin > > > > Mark Libucha schrieb: > >> Thanks, Benjamin (and Karl). I have a follow up question... >> >> How does the authority service get populated with ACLs to begin with? >> >> Thanks, >> >> Mark >> >> >> >> On Thu, Nov 7, 2013 at 10:56 AM, Benjamin Brandmeier wrote: >> >>> Hi Mark, >>> >>> for further experiments: >>> Try calling the webapp like this: >>> http://localhost:8345/mcf-authority-service/UserACLs?username=qwefa >>> >>> Without the username I receive a 400. >>> >>> Benjamin >>> >>> >>> 2013/11/7 Mark Libucha >>> >>>> Hi there, >>>> >>>> Having problems getting my head around the MCF Authority Service. >>>> Please just direct me to the documentation if this information is out there >>>> already. >>>> >>>> Is this service (just) a webapp? >>>> >>>> If so, should running start-webapps.sh install/start it? (I have run >>>> start-webapps.sh, but myhost:8345/mcf-authority-service/UserACLs gives me a >>>> 404.) >>>> >>>> If it's not just a webapp, what else do I need to install/register? >>>> That is, is something like mod-authz-annotate also required in addition to >>>> the webapp? >>>> >>>> Assuming I'm using my own search engine output connector (not using >>>> Solr) how does the search engine call the Authority Service? Via the JSON >>>> API? >>>> >>>> Or should I just dive into the Solr plug-in source? >>>> >>>> Thanks, >>>> >>>> Mark >>>> >>> >>> >> > -- sent with Android K-9 Mail > --089e0163420e0da09e04eab534a5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks, Benjamin. Yes, that works. Much appreciated.
Mark


On Fri, Nov 8, 2013 at 4:24 PM, Benjamin Brandmeier &l= t;bdvlop@gmail.com> wrote:
Evening Mark,

you need to define authority connections.
By calling the authority service with a given username (+domain) the define= d source systems will be queried for the currently existing tokens (e.g. AC= L-IDs). This happens every time a query is performed (Caching not counted).=

Please correct me if I'm wrong.

Benjamin



Mark Libucha <
ml= ibucha@gmail.com> schrieb:
Thanks, Benjamin (and Karl). I have a follow up = question...

How does the authority service get populated with = ACLs to begin with?

Thanks,

Mark



On Thu, Nov 7, 2013 at 10:56 AM, Benjami= n Brandmeier <bdvlop@gmail.com> wrote:
Hi Mark,

for further experiments:
=

Without the username I receive a 400.

Benjamin


2013/11/7 Mark Libucha <mlibucha@gmail= .com>
Hi there,

= Having problems getting my head around the MCF Authority Service. Please ju= st direct me to the documentation if this information is out there already.=

Is this service (just) a webapp?

If so, should running start-webapps.sh install/start it? (I have run st= art-webapps.sh, but myhost:8345/mcf-authority-service/UserACLs gives me a 4= 04.)

If it's not just a webapp, what else do I need to ins= tall/register? That is, is something like mod-authz-annotate also required = in addition to the webapp?

Assuming I'm using my own search engine output connector (not using= Solr) how does the search engine call the Authority Service? Via the JSON = API?

Or should I just dive into the Solr plug-in source?

Thanks,

Mark



-- sent with Android K-9 Mail
--089e0163420e0da09e04eab534a5--