ebsco, proquest configuration?

[Cantor, Scott]

On 11/14/12 2:06 PM, "Don Faulkner" <donf at uark.edu> wrote:

>Would anyone care to share details of a working ebsco or proquest
>configuration?

We use EBSCO, yes. I just release entitlement, nothing fancy.

>I've run into a dead end configuring attribute resolution and release for
>ebsco. We had it working briefly in April, but had to pull it out when it
>broke our google release[1]. Now, I'm trying to put it back in and not
>getting anywhere. I'm getting ebsco's
> "Error 103" message, without much indication what's wrong. i'm not
>getting a lot of help out of ebsco right now. I've been told that they
>only have tools to debug UK Shibboleth users.

That makes, umm, not a lot of sense. Why would the UK be different? I
suspect they use affiliation instead of entitlement, maybe that's the
issue.

>Since we don't yet have directory information to resolve from, I've tried
>eduPersonEntitlement two ways:

No. You can't "create" data in the filter. That isn't how you set
attributes. They have to come from the resolver.

>First, as an AttributeValueString in attribute-filter.xml:
><afp:PermitValueRule xsi:type="basic:AttributeValueString"
>value="urn:mace:dir:entitlement:common-lib-terms" />

That releases the data if it exists.

>Second, as a static data connector in attribute-resolver.xml:
>    <resolver:DataConnector id="staticAttributes" xsi:type="dc:Static">
>        <dc:Attribute id="eduPersonEntitlement">
>            <dc:Value>urn:mace:dir:entitlement:common-lib-terms</dc:Value>
>        </dc:Attribute>
>    </resolver:DataConnector>

That also does only half the work. You cannot generate attributes from a
connector, that's the raw material. You still need attribute definition(s)
with appropriate SAML encoders attached.

-- Scott