Replaces the SSL and service communications certificate in Active Directory Federation Services.
What happens
- The service agent on the server fetches the task from the appliance over outbound HTTPS, port 443.
- The Windows basics first import the certificate into the Windows certificate store (LocalMachine\My).
- The certificate is assigned to the SSL bindings and the service communications role in AD FS. A separate action refreshes chosen relying party trusts from their federation metadata (Dynamics CRM, for one) without touching AD FS's own certificate. If it fails: Rollback puts the previous certificates back on both.
- Verification: the integration checks that both use the new certificate.
Technical details
- Connection
- The integration runs through the service agent on the server. The service agent connects over outbound HTTPS to the appliance, port 443 by default. You open no port into the server.
- Service ports
- 443
- What you need
- The service agent installed on the server. The service agent on an AD FS federation server with the AD FS PowerShell module.
- Platform
- AD FS 3.0 and later, Windows Server 2012 R2 and later
- Actions
- Discovery, Installation, Verification, Rollback
- Integrations
-
windows-adfs1.2.0 - Note
-
- The integration changes both SSL and Service Communications. Service Communications requires RSA 2048, 3072 or 4096 bits with a legacy CSP and KeySpec 1 (AT_KEYEXCHANGE). ECC and CNG are refused before key permissions or bindings change. A separate SSL role in AD FS 2016 and later can use CNG; this integration also changes Service Communications. Microsoft: https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/technical-reference/ad-fs-and-keyspec-property