L2TP/IPsec Issue After Gateway Rename

[TSOL]

Hello Experts

In a Smart-1 Cloud–managed environment, we observed an issue where
L2TP/IPsec (Remote Access VPN) stops working after changing the Security Gateway object name.

As a result of our investigation, we found that the old object name remains in the Subject/CN of the Gateway certificate.
As a test, we reverted the object name back to the original one, and VPN connectivity started working normally.
Based on this behavior, we believe that the object name embedded in the certificate is affecting VPN operation.

When changing the object name of a Security Gateway that uses L2TP,
is it necessary to explicitly delete and reissue the certificate on the Smart-1 side?

Additionally, if there are any Smart-1 Cloud–specific limitations or considerations compared to an on-premises Management Server,
I would appreciate it if you could share them.

Thank you in advance.

[Vincent_Bacher · Accepted solution]

I don't use S1C so i cannot answer the qestion about limitations there.
Regarding Certificate: Yes. You have to delete the old VPN cert and generate a new one.

First remove the old one, then "Add..." 

[the_rock]

Im fairly sure what Vince said is absolutely correct. I have access to 8 clients S1C and regardless if its cloud mgmt or on prem, behavior would be the same when it comes to what you are describing.