idpv3 first look

[Cantor, Scott]

On 7/1/14, 7:54 PM, "Jim Fox" <fox at washington.edu> wrote:
>I'm trying out the idp v3 (idp-distribution-3.0.0-alpha1).

Thank you.

>--------------------
>How do I add jars to the classpath?  I want to use postgres.
>I tried adding a
>
>   java -Djetty.class.path="path-to-pastgresql.jar" ...

I think it's TBD how that will work, but we were just discussing this
Friday and I think the idea is to ship the distribution with an unpacked
war tree that you will populate with third party jars via an overlay
directory, and then run a pack script much like today. That also means we
can build scripts for command line tools that will load the same set of
jars into the classpath, so there won't be two copies of all the jars in
every install tree.

But if you need to tell *Jetty* about a jarfile, that really depends on
how you're deploying Jetty, and the current example is really just us
including our testbed Jetty config at the moment.

With a modern Jetty install, you generally put jars you need loaded into
jetty-base/lib/ext and make sure the ext module is activated in start.ini.
I don't know if the included example start.ini is activating ext or not
offhand.

Really if you're trying to test right now and you have an established
container environment, your best choice is probably to just deploy into
that container as usual and if something breaks it's worth us figuring
that out anyway. I happen to use Jetty myself, so I'll be testing this
with Jetty, but with my jetty-base tree, not this one.

>and I tried putting the jar in jetty's lib dir.

I don't think just putting them into lib will actually do it, the new
versions actually load specific folders under lib/ depending on module
activation.

>How do I specify multiple attribute filter files?

Add resources as needed to conf/services.xml, similar to V2.

>---------------------
>I get a ton of these warnings
>
>16:43:38.623 - WARN
>[net.shibboleth.idp.attribute.filter.spring.BaseFilterParser:139] -
>Element 'PermitValueRule' did not contain an 'id' attribute.  Generated
>id 
>'/AttributeFilterPolicyGroup:CoreFilterPolicy/PermitValueRule:_5ba4f3ad3b3
>8862fabf2c3a34489a7ec' will be used
>
>
>Nobody ever complained before.  I agree that the elements don't have ids,
>but, if your going to use a default, the WARN seems excessive.

If they stay WARN it will be because we decide to formally deprecate not
including an ID, and then it would be appropriate. If we don't deprecated
that, we'll turn down the level.

-- Scott