Skip to Content.
Sympa Menu

metadata-support - [Metadata-Support] Recent InCommon metadata issue question

Subject: InCommon metadata support

List archive

[Metadata-Support] Recent InCommon metadata issue question


Chronological Thread 
  • From: Mike Flynn <>
  • To:
  • Subject: [Metadata-Support] Recent InCommon metadata issue question
  • Date: Fri, 25 Mar 2016 08:41:06 -0700
  • Authentication-results: mail522.prod.linkedin.com x-tls.subject="/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com"; auth=pass (cipher=ECDHE-RSA-AES128-GCM-SHA256)
  • Authentication-results: mail522.prod.linkedin.com; iprev=pass policy.iprev="209.85.192.46"; spf=softfail smtp.mailfrom="" smtp.helo="mail-qg0-f46.google.com"; dkim=none (message not signed) header.d=none; tls=pass (verified) key.ciphersuite="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256" key.length="128" tls.v="tlsv1.2" cert.client="C=US,ST=California,L=Mountain View,O=Google Inc,CN=smtp.gmail.com" cert.clientissuer="C=US,O=Google Inc,CN=Google Internet Authority G2"
The recent issue with the InCommon metadata caused an issue with a single Idp that we connect to (Gallaudet U) who updated their cert.  They get a 500 post auth (I do not have logging in prod greater than INFO due to the volume of the data).

I noted Tom Scavo's email about this issue and I followed his directions for deleting the backing file and restarting Shibboleth but this connection still fails.  I did this process 2 days running in the hopes that it would resolve...  but no joy.

I am not really sure what to do at this point.  The backing files all get date/time stamp of the time I do the restart so I presume they are fine.

--
Mike Flynn

linkedIn / lynda.com

Internal Extension: 359
O. 805-755-1515
C. 805-990-4566

Archive powered by MHonArc 2.6.16.

Top of Page