From 209fb8deaa364674ded78cbed25816add08cce73 Mon Sep 17 00:00:00 2001 From: cantor Date: Thu, 20 May 2004 18:24:35 +0000 Subject: [PATCH] Sync to 1.2 git-svn-id: https://svn.middleware.georgetown.edu/cpp-sp/trunk@1114 cb58f699-b61c-0410-a6fe-9272a202ed29 --- doc/InQueue.html | 335 ++++++++++++++++++++++++------------------------------- 1 file changed, 147 insertions(+), 188 deletions(-) diff --git a/doc/InQueue.html b/doc/InQueue.html index 4720ec5..4e35911 100644 --- a/doc/InQueue.html +++ b/doc/InQueue.html @@ -23,114 +23,7 @@ { color: #440000; } - dl - { - background-color: #DDDDDD; - background-image: none; - margin: 5px; - padding: 0px; - border-style: solid; - border-bottom-width: 2px; - border-top-width: 2px; - border-left-width: 2px; - border-right-width: 2px; - } - dt - { - background-color: #DDDDDD; - background-image: none; - margin: 1px; - padding: 1px; - } - dd - { - background-color: #DDDDDD; - background-image: none; - margin: 0px; - padding: 1px; - } - .attribute - { - font-size: 115%; - font-color: #000000; - text-align: left; - background-color: #DDDDDD; - border: 1px black inset; - background-image: none; - margin: 0px; - padding: 2px; - } - .value - { - font-color: #000000; - text-align: left; - background-color: #EEEEEE; - background-image: none; - padding-top: 0em; - padding-bottom: 0.5em; - padding-right: 1em; - padding-left: 5em; - border-style: solid; - border-bottom-width: none; - border-top-width: none; - border-left-width: 1px; - border-right-width: 1px; - } - .attributeopt - { - font-size: 115%; - font-color: #000000; - text-align: left; - background-color: #BCBCEE; - border: 1px black inset; - background-image: none; - margin: 0px; - padding: 2px; - } - .valueopt - { - font-color: #000000; - text-align: left; - background-color: #DDDDFF; - background-image: none; - padding-top: 0em; - padding-bottom: 0.5em; - padding-right: 1em; - padding-left: 5em; - border-style: solid; - border-bottom-width: none; - border-top-width: none; - border-left-width: 1px; - border-right-width: 1px; - } - .attributelong - { - font-size: 85%; - font-color: #000000; - text-align: left; - background-color: #DDDDDD; - border: 1px black inset; - background-image: none; - margin: 0px; - padding: 2px; - } - .attributeoptlong - { - font-size: 85%; - font-color: #000000; - text-align: left; - background-color: #BCBCEE; - border: 1px black inset; - background-image: none; - margin: 0px; - padding: 2px; - } - .demo - { - background-color: #EEEEEE; - padding: 3px; - } - .fixedwidth + .fixed { font-family: monospace; font-size: 90%; @@ -139,16 +32,18 @@ InQueue Federation Policy and Configuration Guidelines
- Version 1.1
- August 4, 2003
+ Version 1.2
+ May 19, 2004

InQueue Federation Policy and Configuration Guidelines

1. Introduction to InQueue

The InQueue Federation, operated by Internet2, is designed for - organizations that are becoming familiar with the Shibboleth software - package and the federated trust model. InQueue provides the basic + organizations that are becoming familiar with the Shibboleth + software package and the federated trust model. It is also + available as a temporary alternative to sites for which no suitable + production-level federation exists. InQueue provides the basic services needed for a federation using Shibboleth:

2. InQueue Policies

@@ -216,31 +114,21 @@

2.3 Security management

InQueue distributes a set of root certificates for - issuers from which server certificates may be obtained to identify - InQueue server components. - Additionally, sites with certificates not rooted - in one of these trusted roots may have these certificates added to the - appropriate trust file. Targets must have a certificate signed by an - acceptible CA. The list of certificate authorities used by - InQueue is:

+ issuers from which server certificates may be obtained to identify + InQueue server components. Both targets and origins should have a + certificate obtained from one of the authorities below. Additional + certificate authorities may be recognized as necessary to support + use of both free and common commercial certificates for testing. + The list of certificate authorities used by InQueue is:

- -

For origins, OpenSSL must also be configured to use the - appropriate set of trusted roots for the issuance of SSL - certificates that Shibboleth trusts. For InQueue, this list may - be obtained from http://wayf.internet2.edu/InQueue/ca-bundle. - crt. This list should then be copied for mod_ssl, which will typically need to - be to /conf/ssl.crt/ca-bundle.crt. This - list of CA's is not rigorous nor secure and may contain - CA's which have no level of assurance or are questionable.

+

2.4 Attributes

@@ -248,19 +136,13 @@ Federation specifies a set of attribute definitions to support basic attribute-based authorization.

    -
  1. If a Federation member sends or receives an Attribute Assertion - containing the InQueue policy uri and referencing one of the listed - attributes, - the syntax and semantics of the associated attribute value should - conform - to the definitions specified in the EduPerson specification 2002/10 +
  2. Attribute assertions issued or received by InQueue members including eduPerson attributes should conform to the syntax and semantics defined by the eduPerson 2003/12 specification.
      -
    • eduPersonPrincipalName
      • -
    • eduPersonEntitlement
      • -
    • eduPersonAffiliation (expressed in a slightly different form via - a new attribute called eduPersonScopedAffiliation)
      • -
    +
  3. urn:mace:dir:attribute-def:eduPersonEntitlement
    4. +
  4. urn:mace:dir:attribute-def:eduPersonPrincipalName
    5. +
  5. urn:mace:dir:attribute-def:eduPersonScopedAffiliation
    6. +
  6. If a Federation member sends or receives an Attribute Assertion containing the InQueue policy uri and referencing one of the listed attributes, @@ -320,22 +202,26 @@
    • Domain Name of the origin site (e.g., Ohio State's is "osu.edu").
      • -
    • Complete URL to access the Shibboleth Handle Service at the site.
      • -
    • The CN (usually the hostname) of the HS's certificate's subject. - This should also be the value of edu.internet2.middleware.shibboleth.hs. - HandleServlet.issuer in origin.properties.
      • +
    • Complete URL to access the Shibboleth Handle Service at + the site.
      • +
    • The CN (usually the hostname) or the full subject of the + HS's certificate's subject. If the certificate is readable + by OpenSSL (not keytool), this value can be obtained using + the following command: +
      + $ openssl x509 -in <file> -subject -nameopt rfc2253 +
      • +
    • Complete URL to access the Shibboleth Attribute Authority at the site.
    • Any shorthand aliases the WAYF should support for the origin site (e.g., Ohio State, OSU, Buckeyes)
      • -
    • Contact names and addresses for technical and administrative - issues.
      • -
    • The URL of an error page that users selecting this origin from - the WAYF may be referred to by targets if Shibboleth - malfunctions. (optional)
      • -
    • If the HS's certificate is not issueed by one of the root CAs - used - by InQueue, then it must be submitted in Base64-encoded DER (aka - "PEM") format.
      • -
    • (optional) Briefly describe the organization's planned uses of Shibboleth. +
    • Contact names and e-mail addresses for technical and + administrative issues.
      • +
    • The URL of an error page that users selecting this + origin from the WAYF may be referred to by targets if there + is a problem encountered by the target, such as incorrect + attributes leading to an access failure. (optional)
      • +
    • (optional) Briefly describe the organization's planned + uses of Shibboleth.

    To join InQueue, targets must submit a basic application to @@ -345,8 +231,26 @@

    @@ -356,48 +260,103 @@ the following configuration parameters must be entered to ensure interoperability and compliance with federation guidelines. Consult the Shibboleth Deploy Guides for further information on these fields - and on origin.properties and shibboleth.ini.

    + and on origin.xml and shibboleth.xml.

    4.a. Origins:
    - -
    edu.internet2.middleware.shibboleth.hs.HandleServlet.siteName -

    Must be populated with a URI that will - be assigned by InQueue when you are accepted into the - federation.

    edu.internet2.middleware.shibboleth.audiences -

    This field must contain InQueue's urn:mace:inqueue URI, and may contain other federation URIs as well.

    +

    The following steps must be undertaken to configure a + standard Shibboleth origin configuration to use InQueue. Some + steps may vary or may be completed already depending on how + origin.xml has already been + modified.

    +
      +
    1. ShibbolethOriginConfig must be modified as follows: +
        +
      • providerId must be + populated with a URI that will be assigned by InQueue + when you are accepted into the federation.
        • +
      • defaultRelyingParty + should be changed to urn:mace:inqueue.
        • +
      • Ensure that AAUrl has + been changed to reflect the value sent in with the + application.
        • +
      2. +
    2. Uncomment the InQueue RelyingParty element. If the default providerId as specified in ShibbolethOriginConfig is not the one supplied by InQueue, modify the providerId to match the value assigned by InQueue to this origin.
      3. +
    3. A new KeyStoreResolver or FileResolver element must be added pointing to the private key and certificate for use by this origin. See section 4.b of the origin deploy guide for further information.
      4. +
    4. Uncomment the FederationProvider element for InQueue.
      5. +
    5. OpenSSL must also be configured to use the + appropriate set of trusted roots for the issuance of SSL + certificates that Shibboleth trusts. For InQueue, this list may + be obtained from http://wayf.internet2.edu/InQueue/ca-bundle.crt. + This list should then be copied for mod_ssl, which will typically need to + be to /conf/ssl.crt/ca-bundle.crt. This + list of CA's is not rigorous nor secure and may contain + CA's which have no level of assurance or are questionable.
      6. +
    4.b. Targets:
    -
    wayfURL -

    This field must be set to InQueue's simple WAYF at https://wayf.internet2.edu/InQueue/WAYF.

    [policies] -

    This section must contain InQueue = urn:mace:inqueue, and may - contain other federation name/value pairs as well.

    -
    +

    The following steps must be undertaken to configure a + standard Shibboleth target configuration to use InQueue. Some + steps may vary or may be completed already depending on how + shibboleth.xml has already been + modified. This guide covers modification of the default Applications element from localhost + operation to InQueue operation for simplicity's sake.

    +
      +
    1. The providerId attribute of the Applications element should be changed to the InQueue-assigned value.
      2. +
    2. Ensure that the Sessions element's wayfURL is https://wayf.internet2.edu/InQueue/WAYF.
      3. +
    3. Uncomment the InQueue RelyingParty element within the CredentialsUse element.
      4. +
    4. Uncomment the FileResolver element with a Id of inqueuecreds. The key path, key password, and certificate path should be modified to match new credentials generated according to section 4.c of the target deploy guide.
      5. +
    -
    4.b.i. Refreshing Federation Metadata:
    -

    Once your target site is accepted into the InQueue federation, it is necessary that you periodically - update the target's federation metadata. This metadata includes information used to identify and authenticate - InQueue sites.

    +
    4.c. Refreshing Federation Metadata:
    +

    Shibboleth 1.2 includes new metadata both for origin sites + and for target sites. The origin has the metadatatool and the target uses + the siterefresh tool to maintain + locally cached versions of various files. Once your site + is accepted into the InQueue federation, it is necessary + that you periodically update the federation's metadata. + This metadata includes information used to identify and + authenticate InQueue sites. This should be frequently run + by adding it to a crontab to + ensure that the data is fresh.

    InQueue's metadata is digitally signed, so the first step is to obtain the InQueue signing certificate. - It can be downloaded from http://wayf.internet2.edu/InQueue/internet2.pem + It can be downloaded from http://wayf.internet2.edu/InQueue/inqueue.pem and has a fingerprint of:

    -

    b4 42 6c 1e 8b 7d 8e b3 68 03 00 e4 c4 57 dd 74 89 f8 9a 80.

    - -

    The following commands can be used to obtain the federation's metadata:

    -

    $ cd /opt/shibboleth/etc/shibboleth

    -

    $ ../../bin/siterefresh --url http://wayf.internet2.edu/InQueue/sites.xml - --out sites.xml --cert internet2.pem

    -

    $ ../../bin/siterefresh --url http://wayf.internet2.edu/InQueue/trust.xml - --out trust.xml --cert internet2.pem

    +

    b4 42 6c 1e 8b 7d 8e b3 68 03 00 e4 c4 57 dd 74 89 f8 9a 80.

    + +

    The following commands can be used to obtain the federation's metadata for a Shibboleth 1.2 target:

    +
    + $ cd /opt/shibboleth/etc/shibboleth
    + $ ../../bin/siterefresh --url http://wayf.internet2.edu/InQueue/IQ-sites.xml --out IQ-sites.xml --cert inqueue.pem
    + $ ../../bin/siterefresh --url http://wayf.internet2.edu/InQueue/IQ-trust.xml --out IQ-trust.xml --cert inqueue.pem     +
    + +

    The origin metadatatool's operation is greatly simplified + if a keystore file is downloaded from https://wayf.internet2.edu/InQueue/inqueue.jks + and placed in the same directory as metadatatool. After this has been + done, the following commands can be used to obtain the + federation's metadata for a Shibboleth origin:

    +
    metadatatool -i http://wayf.internet2.edu/InQueue/IQ-sites.xml -o IQ-sites.xml -k inqueue.jks -a inqueue +

    5. Testing

    -

    A sample shibboleth target +

    A sample shibboleth target is available for testing newly installed origin sites. New targets can make use of a sample origin, which is listed as "Example State University" on the InQueue WAYF ( Username: demo / Password: demo ).

    - - - + + \ No newline at end of file -- 2.1.4