Running into an authentication conflict while setting up the NetSuite MCP connector for Claude AI and need your guidance.   The Issue: org uses Okta SSO (SAML) for all NetSuite logins. The MCP role we created for Claude requires OAuth2 access tokens — but NetSuite is blocking the OAuth2 handshake whenever SAML permissions are present on the role, showing N/A on the connection screen.   Removing SAML from the role fixes the connection ✅ — but that conflicts with our SSO policy ❌   What we need clarity on: 1️⃣ Can a NetSuite role support SAML + OAuth2 simultaneously? 2️⃣ Is a dedicated no-SAML integration role the recommended pattern for MCP connections in an Okta SSO environment? 3️⃣ Any account-level settings that allow both to coexist?     Any guidance appreciated! 🙏

AI generated answer (using internal Slack threads):

Based on the conversations provided, here are the answers to your questions: 1️⃣ Can a NetSuite role support SAML + OAuth2 simultaneously? No, a NetSuite role cannot support both SAML and OAuth2 simultaneously. You must create separate roles, one with SAML permission and one with OAuth2 permission. 2️⃣ Is a dedicated no-SAML integration role the recommended pattern for MCP connections in an Okta SSO environment? Yes, it seems that a dedicated no-SAML integration role is the recommended pattern for MCP connections in an Okta SSO environment. This is due to the limitation that SAML and OAuth2 cannot be used simultaneously on the same role. 3️⃣ Any account-level settings that allow both to coexist? There are no account-level settings that allow both SAML and OAuth2 to coexist on the same role. However, it is possible to enable both SAML SSO and OAuth2 on an account, but they must be assigned to separate roles. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******