Skip to Content.
Sympa Menu

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

Subject: InCommon metadata support

List archive

Re: [Metadata-Support] Recent InCommon metadata issue question


Chronological Thread 
  • From: Mike Flynn <>
  • To:
  • Subject: Re: [Metadata-Support] Recent InCommon metadata issue question
  • Date: Fri, 25 Mar 2016 10:05:27 -0700
  • Authentication-results: mail521.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: mail521.prod.linkedin.com; iprev=pass policy.iprev="209.85.192.44"; spf=softfail smtp.mailfrom="" smtp.helo="mail-qg0-f44.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"
There is nothing in the logs...

On Fri, Mar 25, 2016 at 9:27 AM, Cantor, Scott <> wrote:
On 3/25/16, 12:21 PM, " on behalf of Mike Flynn" < on behalf of > wrote:



>They hit my box - it goes back to them for auth.  It comes back to me and gives them a 500.  They say they changed cert recently and this failure occurred after that.

Has to be something in the SP log for me to really react to, a 500 could mean anything. If there's no SP information in either log, then I guess it's an IIS layer issue.

Changing a certificate might break SAML, but you certainly know what that looks like in the log.

-- Scott




--
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