Forum Discussion

Copper Contributor

Nov 06, 2017

Solved

ADFS 3.0 new token-signing cert not in federationmetadata

Last week a added a secondary, internally signed, token-signing certificate to our ADFS 3.0 farm in advance of the cert rollover later this week. When running a get-adfsproperties to validate we see ...

windows server

Sloan Ozanne
Nov 13, 2017
Apologies.......failed to post an update after we resolved it.

Ended up having to reboot the ADFS servers. Cycling the ADFS service wasn't enough. Likely some other internal issue that needs to be looked at, and will, but this specific problem with the metadata is resolved.

Sloan Ozanne

Copper Contributor

Nov 13, 2017

Apologies.......failed to post an update after we resolved it.

Ended up having to reboot the ADFS servers. Cycling the ADFS service wasn't enough. Likely some other internal issue that needs to be looked at, and will, but this specific problem with the metadata is resolved.

Martin Achleitner
Copper Contributor
Jan 02, 2018
Hello,

we have a similar issue with our federationmetadata.xml

We generated new token signing and encryption certificates on Dec.22 2017 but just the token signing certificate appears in the federationmetadata.xml very strange.

The ADFS servers have been restarted a few days after the certificate generation by auto reboot after installing windows updates.

here ist the output of the web-request command:

PS C:\WINDOWS\system32> $metadata = Invoke-WebRequest -Uri "https://server.domain.com/federationmetadata/2007-06/federationmetadata.xml"
([XML] $metadata.Content).EntityDescriptor.RoleDescriptor.KeyDescriptor

use KeyInfo
--- -------
encryption KeyInfo
signing KeyInfo
signing KeyInfo

Does anyone have an idea why the new token encryption certificate not in the federationmetadata ?

Best regards

Martin