<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 10/30/13 6:31 PM, Thomas Jones
wrote:<br>
</div>
<blockquote
cite="mid:CAAtzDquC5=mN5rNuivgs8Q2JZmmXZ-GhiAEMvpOJgnBAcc=tjA@mail.gmail.com"
type="cite">
<div dir="ltr">Good Afternoon Everyone.
<div><br>
</div>
<div>I'm following shibs (IdP) and google docs in order to
integrated these two apps. It's working, but I'm worry about
what the logs shows (entry 17:16:26.930 second line):</div>
</div>
</blockquote>
<br>
<br>
Hmmm, yeah, this didn't look right to me....<br>
<br>
<blockquote
cite="mid:CAAtzDquC5=mN5rNuivgs8Q2JZmmXZ-GhiAEMvpOJgnBAcc=tjA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
<div>17:16:26.930 - TRACE
[org.opensaml.saml2.metadata.provider.AbstractMetadataProvider:538]
- Found entity descriptor for entity with ID <a
moz-do-not-send="true"
href="http://google.com/a/mygoogledomain.com">google.com/a/mygoogledomain.com</a>
but it is no longer valid, skipping it.</div>
</div>
<br>
</div>
</blockquote>
<br>
<br>
Turns out this there is a code path where this validity check and
associated TRACE level message is being done erroneously. So
there's a bug. Looks like it was introduced in Oct 2013. I guess
noone noticed it in 5 years, probably because people tend not to log
on TRACE that often or look at the output that closely (at least I'm
inferring). It doesn't actually hurt anything operationally, just
the incorrect log message and an unnecessary validity check.<br>
<br>
Anyway, you can safely ignore it. You're not doing anything wrong.
I'll open an issue and fix.<br>
<br>
<br>
<br>
</body>
</html>