On Fri, 21 May 2010, Andy Swiffin wrote: > 2c) > SP has old metadata > User goes to SP which directs user to the UK Federation WAYF > UK Fed Wayf has NEW metadata and sends the user to the 2.1 IdP to = > authenticate > SP will look up our ENTITYID in its OLD metadata and then go to 1.3 IdP = > for attributes > BUST > > OOPS. =20 > > This explains the split personality which I'd observed on just a few SPs > = which I'd blamed on them, sorry! > > My apologies for those who've followed this approach and been bitten by > it = - I'm still thinking of a work around! Of course, in an ideal > world, or = even a world where bodies actually did what they'd already > agreed to do, = none of this would be a problem (for more than a > day).... And you know what ... I don't think we should care too much about that. It's a failure on the part of the SP. They've been told they need to keep their metadata regularly updated, and they have chosen not to for whatever reason. So as long as you have understanding library colleagues, and maybe as Adrian says you're willing to go the extra mile to give the lamer providers a prod when you notice them, I'd say it's not your fault and don't worry about it. Might be a different story if you have highly-strung library colleagues though :) This problem is going to keep biting the lamer providers over the next couple of months, so you'd hope they'd get their act together and sort it. Jethro. . . . . . . . . . . . . . . . . . . . . . . . . . Jethro R Binks Computing Officer, IT Services, University Of Strathclyde, Glasgow, UK