ADFS 3.0 - Can the metadata.xml, specifically entityID signature change on the fly and does this break a relying party trust

Hi All,

We have SSO setup with a SaaS provider as  a relying party trust.
The login broke to the SaaS application for several hours and was only fixed after we re-sent the metadata xml file.
The main change in the current and previous xml file was the <EntityDescriptor ID

The main question is: How can this change? Would it require human intervention to change or can it change on the fly or in response to some event?

AndyIt ConsultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AndyIt ConsultantAuthor Commented:
I think I may have found a clue.

On 01/12/2017 the Token-Decrypting self signed certificate renewed, although it seems to have taken 6 days to cause an issue, this is the nearest change I can find on the ADFS server farm. I assume this can change the metadata? and why 6 days?

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.