Configuring a file-backed HTTP resource for attribute filters

[Wessel, Keith]

I'm not sure if this is the same as the bug you referenced, Rod, but I looked at the web server logs on the system serving the attribute filter defitions, and it has a response code of 304 (not modified). I could, of course, prime the pump by manually fetching the file before IDP start-up. My question is should I need to do this, or is this a bug?

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Rod Widdowson
Sent: Monday, July 20, 2015 11:32 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Configuring a file-backed HTTP resource for attribute filters

I don't think it is the case, but you might be being caught by JSE-14 (https://issues.shibboleth.net/jira/browse/JSE-14). But that bites during refresh (it is however a bit of a block on deploying this...)

The red flag for me is the https bit. Is there anything odd going on there?  But I'm afraid you'll need to turn on logging, possibly for the Apache http client as well...

Sent from my iPad

> On 20 Jul 2015, at 16:00, Wessel, Keith <kwessel at illinois.edu> wrote:
> 
> Well, at least it looked simple. :)
> 
> After adding it, with the appropriate edits to the URL and backing file, I'm getting the error:
> 
> 2015-07-20 09:47:37,606 - WARN [net.shibboleth.ext.spring.resource.FileBackedHTTPResource:117] - FileBackedHTTPResource [ 
> https://hostname.removed.edu/itrust-af/shib-test-idp.cites.illinois.edu.xml|ServletContext 
> resource [/services/shib-idp/opt/idp/conf/itrust-test-attribute-filter.xml]] HTTP resource was inaccessible for getInputStream(), trying backing file.
> 
> And of course the backing file doesn't exist yet.
> 
> I can wget this URL fine from the command-line on the IDP. Is there something special I need to do because it's https?
> 
> If need be, I can turn my logging up to debug, but I'd suspect I'm just missing something.
> 
> Keith
> 
> -----Original Message-----
> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Rod Widdowson
> Sent: Monday, July 20, 2015 4:40 AM
> To: 'Shib Users' <users at shibboleth.net>
> Subject: RE: Configuring a file-backed HTTP resource for attribute filters
> 
>> The bean definition from the file-backed http resource page on the wiki
>> makes sense, but I'm not sure where to put it and how to make it work
>> alongside the existing local file resource.
> 
> It's entirely up to you how you structure this.
> 
> For a one off configuration I'd just bung it inline:
> 
>    <util:list id ="shibboleth.AttributeFilterResources">
>        <value>%{idp.home}/conf/attribute-filter.xml</value>
>        <bean
> class="net.shibboleth.ext.spring.resource.FileBackedHTTPResource"
>              c:client-ref="shibboleth.FileCachingHttpClient" 
> 
> c:url="http://another.server.example.org/path/to/different/file.xml"
> 
> c:resource="/var/shibboleth/caches/resourcecache/differentFile.xml"/>
> 
>    </util:list>
> 
> But you can have the bean declared in a separate file (global.xml or another
> file) and have a <ref bean="whatever"/> inside the <util:list>.  The
> service.properties beans are probably of more interest to people setting up
> automated installations (like federations).
> 
> /R
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net