 |
 |
Hi Alistair Not heard of the certificate issue before - would be interested to talk about that more if you want to contact me off list. On the use of the WAYFs by publishers, JISC Collections have just issued an ITT to look in to these sort of problems and to make recommendations based on experience to date. Hopefully this will help here. We use multivalued attributes and haven't had any problems to date. Again, happy to talk to suppliers if you want to contact us off list. Best wishes Nicole -----Original Message----- From: Discussion list for Shibboleth developments <[log in to unmask]> To: [log in to unmask] <[log in to unmask]> Sent: Wed Feb 04 08:23:46 2009 Subject: Issues Has anyone else had these sort of issues with suppliers who are in the federation? - Asking for signing certificates to be sent to a supplier, so a record must be kept of who gets what and when, in case the cert needs renewing - Not using the federation wayf and therefore making visible test entities - Not supporting SDSS legacy entityIDs, making resources inaccessible to federation members. - Not supporting test entities due to dubious "trust" methods (screen- scraping the fed wayf, where test entities are invisible) - Difficulty applying multi-valued attributes to resource partitioning. are there supplier guidelines for working with the federation, its metadata and its members, or can we expect more weird and wonderful implementations to surface? Alistair -------------- mov eax,1 mov ebx,0 int 80h