Shibboleth to SciQuest integration

[Cantor, Scott]

On 1/30/14, 9:44 AM, "Akiko" <akiko.simmons at tulsacc.edu> wrote:

>I am very new to Shibboleth and we finally got finished
>CAS-Shibboleth-O365
>integration.  Now, we need to setup CAS-Shibboleth-Sciquest.  We only have
>documentation which has Metadata URL, and example of attribute-filter.xml
>and attribute-resolver.xml.  I'd like to have some step by step
>instructions, but I can't find it any where.  I even don't know which xml
>files and other files need to be configured. :(

Then your first step is to read the documentation, particularly in
understanding what each file is for and whether it matters for day to day
operations. If you're approaching this as software you can essentially
treat as a black box, you won't be successful and probably should evaluate
different options that suit you better.

The basic steps in federating with an SP depend on trust. For federation
members of InCommon, the steps are purely attribute centric. The metadata
required is already loaded. You have to know what the service's attribute
requirements are, whether you can meet them, and you have to release them
as required to the service in the filter policy. Whether you have to
modify the resolver configuration depends on what you have already and
what the service needs.

For one-off services that are not part of a federation like InCommon, you
have to establish a trusted source of metadata, which in most cases is
going to be a one-time addition of static metadata to a local file, which
unfortunately means every change to that service's metadata involves
manual communication and adjustment. Then the rest of the steps are
basically the same.

-- Scott