Been using SDF and the CLI for a long time. Trying to add M2M credentials for a new account but I keep getting the error Server error. Verify the arguments of the command and that the account has the following features enabled: OAuth 2.0 and SuiteCloud Development Framework. Updated the CLI and confirmed that OAuth and SDF are enabled in the account but still no joy. Anybody else encounter/get around this?

can you post the command and arguments you're passing? The first part of that error message would apply

Bringin in my colleague @Tom. He’s the one hitting this.

Thanks @starlingMark. @Xmun the command we used was (With omitted values)

suitecloud account:setup:ci --account --authid --certificateid --privatekeypath

. We have tried it on Ubuntu and OSX using

suitecloud

instances that already manage other accounts using the same cert.

maybe stating the obvious but, can you confirm: 1. the SuiteCloud Development Integration bundle is actually installed in the target account you're trying to hit 2. you have an entry in the OAuth 2 Client Credentials list, with a certificate id against the above app, which matches what you're passing for --certificateid

Boom! number one was the issue. I created an integration called SuiteCloud Development Integration with the same settings as the other accounts we managed. I did not realize it was a bundle that needed to be installed. Thanks for the help @Xmun. I was able to get things connected after the update.

badabingbadaboooom

@Tom, I didn't realize that either!

If my esteemed colleague @darrenhillconsulting didn’t know then I feel 50% less dumb 😂

Just as a follow up. The SuiteCloud Development Integration also gets installed in the account when you run Browser Based Authentication for the first time through your SuiteCloud SDK client of choice (plugin/cli). This happens through the Authorization Code Grant flow.

Ah - that makes more sense!

i found another (admittedly quite silly but clearly possible because it happened) way to get this error: you need to have login access to the account! or more specifically, the entity on the certificate entry in the NS account needs to have access