JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH Archives

JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH  October 2009

JISC-SHIBBOLETH October 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Certificate sequence issues with JSTOR

From:

Patrick Maginn <[log in to unmask]>

Reply-To:

Discussion list for Shibboleth developments <[log in to unmask]>

Date:

Fri, 30 Oct 2009 09:26:08 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (199 lines)

Hi Steve,

Have you tried changing the pem file:


The latter 'GlobalSignCertificateChain.pem' file contains the following
certificates, in this order:
GlobalSign Root CA
GlobalSign Primary Secure Server CA
GlobalSign Server Sign CA

To:
GlobalSign Server Sign CA
GlobalSign Primary Secure Server CA
GlobalSign Root CA


Regards

Patrick

Patrick Maginn
Technical Specialist,

Salford Software Ltd,
Lancastrian Office Centre
Talbot Road, Old Trafford
Manchester, M32 0FP
Tel: +44 (0) 161 906 1002
Fax: +44 (0) 161 906 1003

www.salfordsoftware.co.uk
The leader in Identity Management Solutions
--------------------------------------------------------------------------------------------------------------
Important Information

This email is confidential and may contain privileged material. If you are not the intended recipient then you must not copy it, forward it, use it for any purpose, or disclose it to another person. Instead please return it to the sender immediately. Please then delete your copy from your system.

Please also note that the author of this email cannot conclude any contract on behalf of Salford Software Ltd by email.

Company Registered in England No. 2252625. VAT Reg. No. 519613442
Academic Enterprises. University of Salford, Salford. M5 4WT
________________________________________
From: Discussion list for Shibboleth developments [[log in to unmask]] On Behalf Of Steve Holden [[log in to unmask]]
Sent: 29 October 2009 16:51
To: [log in to unmask]
Subject: Certificate sequence issues with JSTOR

Hi, folks

We've been trying to permit access to JSTOR via our Shib 1.3 IdPs
for some time now (on and, mostly, off) but appear to be falling
foul of their certificate checking - which seems to be stricter about
the sequence of links in the certificate chain than that in other SPs

As JSTOR have now suggested I ask other .ac.uk folk, I've taken
the liberty of including a section of their latest email below
which explains the issue in more detail, and which seems rather
similar to this post by their lead developer to the Shib Users list:
http://groups.google.com/group/shibboleth-users/browse_thread/thread/dba
8e03a3ce1670b?pli=1


Our idp.xml config contains the following stanza:

<Credentials xmlns="urn:mace:shibboleth:credentials:1.0">
  <FileResolver Id="ukfederationCredentials">
    <Key>
      <Path>file:/etc/pki/tls/private/idp.brighton.ac.uk.pem</Path>
    </Key>
    <Certificate>
      <Path>file:/etc/pki/tls/certs/idp.brighton.ac.uk.pem</Path>

<CAPath>file:/etc/pki/tls/certs/GlobalSignServerSignCA.pem</CAPath>

<CAPath>file:/etc/pki/tls/certs/GlobalSignPrimarySecureServerCA.pem</CAP
ath>
      <CAPath>file:/etc/pki/tls/certs/GlobalSignRootCA.pem</CAPath>
    </Certificate>
  </FileResolver>
</Credentials>

I've tried various permutations of the Path and CAPath lines, but to no
avail.


I'm assuming that idp.xml is the relevant file here - rather than the
Apache config.
But here's our standard certificate stanza from the Apache config:

SSLEngine on
SSLCipherSuite
ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile  /etc/pki/tls/certs/idp.brighton.ac.uk.pem
SSLCertificateKeyFile /etc/pki/tls/private/idp.brighton.ac.uk.pem
SSLCertificateChainFile
/etc/pki/tls/certs/GlobalSignCertificateChain.pem
SSLVerifyClient none
SSLVerifyDepth  10

The latter 'GlobalSignCertificateChain.pem' file contains the following
certificates, in this order:

GlobalSign Root CA
GlobalSign Primary Secure Server CA
GlobalSign Server Sign CA


Has anyone else experienced a similar problem?
If so, could you post the appropriate lines from you JSTOR-compliant
config?


I've double-checked the Federation and Shib guides and JSTOR's own Shib
page:
http://www.ukfederation.org.uk/content/Documents/Setup1p3IdP
https://spaces.internet2.edu/display/SHIB/IdPPKIConfig
http://www.jstor.org/page/info/resources/librarians/tech.jsp#shibboleth

Apologies if I'm missing something obvious.
This is the first SP with whom we've experienced this problem, and it's
a little awkward to debug.

BTW, am posting here rather than UK Federation Discuss, as this list
seems
more widely used these days.

Kind regards,
Steve Holden
Principal Systems Officer
Network Services
University of Brighton


Date: 28 Oct 2009
Department: JSTOR Tech Support

We are still seeing a certificate chaining error in our SSL activity
logs.  Here's the chain from our logs:

2009-10-21 05:55:27,618 *** Certificate chain
2009-10-21 05:55:27,619 chain [0] = [
2009-10-21 05:55:27,619 Subject:
[log in to unmask], CN=idp.brighton.ac.uk,
O=University of Brighton, C=GB
2009-10-21 05:55:27,619 Issuer: CN=GlobalSign ServerSign CA,
OU=ServerSign CA, O=GlobalSign nv-sa, C=BE

2009-10-21 05:55:27,620 chain [1] = [
2009-10-21 05:55:27,620 Subject: CN=GlobalSign Root CA, OU=Root CA,
O=GlobalSign nv-sa, C=BE
2009-10-21 05:55:27,620 Issuer: CN=GlobalSign Root CA, OU=Root CA,
O=GlobalSign nv-sa, C=BE

2009-10-21 05:55:27,621 chain [2] = [
2009-10-21 05:55:27,621 Subject: CN=GlobalSign Primary Secure Server CA,
OU=Primary Secure Server CA, O=GlobalSign nv-sa, C=BE
2009-10-21 05:55:27,621 Issuer: CN=GlobalSign Root CA, OU=Root CA,
O=GlobalSign nv-sa, C=BE

2009-10-21 05:55:27,622 chain [3] = [
2009-10-21 05:55:27,622 Subject: CN=GlobalSign ServerSign CA,
OU=ServerSign CA, O=GlobalSign nv-sa, C=BE
2009-10-21 05:55:27,622 Issuer: CN=GlobalSign Primary Secure Server CA,
OU=Primary Secure Server CA, O=GlobalSign nv-sa, C=BE

Thus, chain[0] is your cert. It should be signed by chain[1], and so on,
so that the signing order is

chain[3] -> chain[2] -> chain[1] -> chain[0]

but instead, the signing order is

chain[1] -> chain[2] -> chain[3] -> chain[0]
In order for this to work, the certificates need to be in the following
order.

Subject: [log in to unmask],
CN=idp.brighton.ac.uk, O=University of Brighton, C=GB
Subject: CN=GlobalSign ServerSign CA, OU=ServerSign CA, O=GlobalSign
nv-sa, C=BE
Subject: CN=GlobalSign Primary Secure Server CA, OU=Primary Secure
Server CA, O=GlobalSign nv-sa, C=BE
Subject: CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE


We do appreciate that other Shibboleth Service Providers do not consider
an out of order chain to be an error. This "pickiness" is a result of
our particular Java SSL implementation which requires that the chain
order is strictly adhered to. I am afraid that there is nothing we can
do about this in the short term, but we do recognize the problems caused
for institutions such as yourselves, and so we are working with our
platform developers, and consulting with the wider Shibboleth community
to find a workable solution to this issue.

I do know that other UK Federation IdPs have run into this same cert
chaining issue with JSTOR and have been able to resolve the issue, so
hopefully you should be able to get some help from the Uk Federation or
other UK University.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

November 2023
February 2023
January 2023
November 2022
October 2022
September 2022
June 2022
January 2022
November 2021
October 2021
September 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
December 2015
November 2015
September 2015
August 2015
June 2015
April 2015
March 2015
February 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager