issue with CDS 1.2.0?

[Rod Widdowson]

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]