5.2.5. Dynamic Participant Renewal, Revocation, and Expiration

5.2.5.1. [Minor] Local DomainParticipant did not detect more recent expiration date in updated Identity Certificate

After updating the Identity Certificate of a DomainParticipant to one with a more recent “Not After” expiration date, only remote DomainParticipants accounted for the updated expiration date and banished the expired DomainParticipant accordingly.

The local DomainParticipant still notified the user about the upcoming expiration on the previous “Not After” date. The updated Identity Certificate would expire without a user notification from the Security Plugins.

Now, the local DomainParticipant correctly recognizes the new expiration date when notifying about certificate expiration.

Though both local and remote DomainParticipants now work as expected, RTI recommends using a later expiration date any time you update an Identity Certificate.

[RTI Issue ID SEC-2691]