Change to the NetSuite SAML Certificate in the NetSuite SP Metadata
Your NetSuite Account ID: 1125535
You are receiving this notification because you are using SAML Single Sign-on in your NetSuite account. On June 13, 2018, the SAML certificate referenced in the NetSuite Service Provider (SP) metadata will expire. We are in the process of renewing the NetSuite SAML certificate, and will be updating the NetSuite SP metadata file. We will release the change in the scheduled e-fix to all sandbox accounts on June 6, 2018 and to all production accounts on June 7, 2018.
The change to the SP metadata will particularly affect those SAML customers who are:
Using the SP-initiated flow with a signed request.
Using the IdP-initated flow with encrypted assertions (or parts of the assertion that are encrypted).
Using the Single Logout functionality.
These customers must update their IdP with the new certificate information to ensure these features continue to work after the change goes into effect.
Note: This change affects only those SP-initiated flows that contain a signed request. SP-initiated flows with requests that are not signed, and IDP-initiated flows that do not contain encrypted assertions, will continue to work as they did before this change goes into effect.
Upload the new NetSuite SP metadata file to your IdP, or at least upload a new certificate file, for all accounts in which you use SAML. Your sandbox accounts will be updated on June 6, 2018 and your production account will be updated on June 7, 2018.
What is Changing?
On June 13, 2018, the SAML certificate referenced in the NetSuite Service Provider Metadata will expire. We will be renewing the NetSuite SAML certificate, and updating the NetSuite Service Provider (SP) Metadata as follows:
Sandbox accounts: June 6, 2018.
Production accounts: June 7, 2018.
Those customers that might be affected by this change should update the NetSuite Service Provider (SP) metadata information with your identity provider (IdP) after we publish the new certificate (after the e-fix has been pushed to your account).
Upload the new NetSuite SP metadata file.
Upload a new certificate file.
For more information, see the following help topics:
Please do not reply directly to this e-mail, as we are unable to process it. If you are not the appropriate recipient for this type of communication, you may either unsubscribe (below) or contact us via your Account Manager or Customer Support.
2955 Campus Drive, Suite 250 San Mateo, CA 94403-2511 650-627-1000
Hi Dylan, The Okta OIN Netsuite app currently does not have encryption turned on and we do not upload the Netsuite certificate in the Okta setup. The only way you could be impacted by this change on Netsuite is if you used the SAML wizard application setup with encryption turned on and you used the Netsuite certificate for encryption. If you added the OIN Netsuite application in Okta there are no changes that need to be made in Okta.