I'm setting up the SuiteCloud CLI (version 3.1.2) on a Linux/WSL machine and need to authenticate via suitecloud accountsetupci. I understand this now requires OAuth 2.0 Machine-to-Machine (Client Credentials) authentication as of NetSuite 2024.2 — TBA is no longer supported for this command. I have Administrator access. Please give me the exact step-by-step configuration, including all checkbox labels and field values, for: 1. Integration Record — Should I use the built-in "SuiteCloud Development Integration" application, or do I need to create a new Integration Record? If I need to create a new one (Setup → Integration → Manage Integrations → New), tell me: - Exact label of every checkbox under the Authentication tab - Which to check and which to uncheck (specifically: Token-Based Authentication, Authorization Code Grant, Client Credentials (Machine to Machine) Grant, any others) - Which OAuth 2.0 Scope checkboxes are required for SDF deployments (e.g. REST Web Services, RESTlets, SuiteAnalytics Connect, or an SDF-specific scope) - Any other required fields 2. Role permissions — What is the minimum set of permissions a custom role needs for full SDF use (project:deploy, file:import, object:import, object:list, project:validate)? Please list each permission by its exact label and level (View/Edit/Full). 3. OAuth 2.0 Client Credentials (M2M) Setup (Setup → Integration → Manage Authentication → OAuth 2.0 Client Credentials (M2M) Setup → Create New) — confirm the exact field names and the certificate format expected (X.509 PEM, .cer, .crt?). 4. Account ID — Where exactly do I find the value I should pass to --account (production vs sandbox format)? And when do I need to pass --domain? Please base your answer on the current NetSuite release, not older TBA-era documentation.

AI generated answer (using internal Slack threads):

1. Integration Record - You can use the built-in "SuiteCloud Development Integration" application, but it's recommended to create a new Integration Record for better control and management. - Go to Setup → Integration → Manage Integrations → New - Under the Authentication tab, you will find the following checkboxes: - Token-Based Authentication - Authorization Code Grant - Client Credentials (Machine to Machine) Grant - For your use case, uncheck Token-Based Authentication and Authorization Code Grant, and check Client Credentials (Machine to Machine) Grant. - For OAuth 2.0 Scope, check REST Web Services and RESTlets. These are typically required for SDF deployments. You may need to check other scopes depending on your specific use case. - Other required fields include Name (unique name for the integration), State (enabled or disabled), and User Credentials are Disabled (check this box). 2. Role permissions - The minimum set of permissions a custom role needs for full SDF use are: - SDF Projects: Full - Log in using Access Tokens: Full - Web Services: Full - User Access Tokens: Full - Manage OAuth 2.0 Client Configurations: Full - Manage OAuth 2.0 Client Configurations: Full - Manage OAuth 2.0 Client Configurations: Full 3. OAuth 2.0 Client Credentials (M2M) Setup - Go to Setup → Integration → Manage Authentication → OAuth 2.0 Client Credentials (M2M) Setup → Create New - The exact field names are: Name, Certificate, and Private Key. - The certificate format expected is X.509 PEM. 4. Account ID - You can find your Account ID under Setup → Integration → Web Services Preferences. The value you should pass to --account is the Account ID listed here. - You need to pass --domain when you are working with a sandbox account. The format is typically

https://<ACCOUNT_ID>.<http://suitetalk.api.netsuite.com|suitetalk.api.netsuite.com>

. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******