issue with CDS 1.2.0?

[Caskey, Paul]

showUnusableIdPs="true" should take care of that, right?
If so, I have that set for this DiscoveryServiceHandler.

And, there are no metadata filters (yet).

> -----Original Message-----
> From: users-bounces at shibboleth.net [mailto:users-
> bounces at shibboleth.net] On Behalf Of Chad La Joie
> Sent: Tuesday, March 20, 2012 10:15 AM
> To: Shib Users
> Subject: Re: issue with CDS 1.2.0?
> 
> Is this a case of items being filtered out before being displayed as opposed to
> anything to do with the metadata itself?
> 
> On 3/20/12 11:11 AM, Caskey, Paul wrote:
> > I tried deleting the existing spool file and it did download a new file, but still
> does not show up in the DS.
> >
> > Here's the log:
> > 10:02:36.441 - INFO
> [org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvide
> r:423] - New metadata succesfully loaded for
> 'http://www.protectnetwork.org/protectnetwork-metadata.xml'
> >
> > 10:02:36.441 - INFO
> >
> [org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvide
> > r:271] - Next refresh cycle for metadata provider
> > 'http://www.protectnetwork.org/protectnetwork-metadata.xml' will occur
> > on '2012-03-20T18:02:36.395Z' ('2012-03-20T13:02:36.395-05:00' local
> > time)
> >
> > No WARN or ERROR messages in the log.
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: users-bounces at shibboleth.net [mailto:users-
> >> bounces at shibboleth.net] On Behalf Of Rod Widdowson
> >> Sent: Tuesday, March 20, 2012 5:08 AM
> >> To: 'Shib Users'
> >> Subject: RE: issue with CDS 1.2.0?
> >>
> >> Paul,
> >>
> >> A major motivation point of the 1.1.3-> 1.2 upgrade was that no
> >> configuration change should be needed; but that you could make
> >> changes to take advantage of all the new options if you wanted.  So
> >> if something is needed, well that would be a bug.
> >>
> >> I've not been able to reproduce this locally, so I'm not sure what to
> suggest.
> >> AFAICS you are correctly configured.
> >>
> >> I know you'll have checked the logs at debug so I won't offend you by
> asking.
> >> Have you tried deleting the spool file
> >> (/opt/shibboleth-ds/metadata/protectnetwork-metadata.xml) just in
> >> case that is implicated?
> >>
> >> /Rod
> >>
> >>
> >>> -----Original Message-----
> >>> From: users-bounces at shibboleth.net
> >>> [mailto:users-bounces at shibboleth.net] On Behalf Of Caskey, Paul
> >>> Sent: 19 March 2012 21:28
> >>> To: users at shibboleth.net
> >>> Subject: issue with CDS 1.2.0?
> >>>
> >>> I'm having trouble getting the new DS to use a metadata source in my
> >>> config which contains only one entry.  This has been in the config
> >>> for years and only 1.2.0 is having a problem (identical config in
> >>> 1.1.3 works as expected).
> >>>
> >>> For example, we have a categorized (list of lists=true) DS which
> >>> lists protectnetwork.org as its own "federation" in the left side text box.
> >>>
> >>> Upgrading an existing CDS from 1.1.3 to 1.2.0 makes protectnetwork
> >>> disappear from the CDS page (no changes were made to wayfconfig.xml
> >>> during the upgrade).  I've tried enclosing their metadata in an
> >>> EntitiesDescriptor, but that didn't help.  I can put their entity
> >>> metadata into
> >> either fed1 or fed2 metadata and it shows up in the list just fine.
> >>>
> >>> Here's the relevant config (fed1 and fed2 are listed in the CDS,
> >>> while
> >> protectnetwork is not):
> >>>
> >>
> >>
> >> [Snip]
> >>
> >> --
> >> To unsubscribe from this list send an email to users-
> >> unsubscribe at shibboleth.net
> > --
> > To unsubscribe from this list send an email to
> > users-unsubscribe at shibboleth.net
> --
> To unsubscribe from this list send an email to users-
> unsubscribe at shibboleth.net