Okta single sign on failing for sandbox post 2024.2 release

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that the issue with Okta Single Sign-On (SSO) failing for the sandbox post 2024.2 release might be due to the different assertion URL needed for SAML/OAUTH based SSO. When a sandbox is refreshed, it can break the SSO with Okta. However, there are some potential solutions to this issue: 1. You could have two icons in Okta for NetSuite - one for Production and one for Sandbox. This way, you can use the same LDAP group for both NetSuite Production and Sandbox, and after refresh, it shouldn't break. 2. You can follow the steps in the NetSuite help documentation to configure the sandbox to be SSO as well via Okta. The link to the documentation was shared in the conversation, but you need to replace the '5s' in the URL with your company ID. This process was confirmed to work by a user who uses G Suite as their IDP and recently enabled access to their Sandbox. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******