Below s what your POST request should look like.Please note the password might need the password+token concatenated:
password: lorem-ipsum-d //**NOTE YOU MIGHT NEED TO DO PASSWORD+TOKEN**
The request parameters (grant_type, client_id and so on) must be sent in the request body . The docs mention this (note the phrase example request body) but they aren't very explicit about this requirement.
You will need to:
Provide the consumer key/secret from the connected app
Ensure that the vendor is setup as a user in your environment
The vendor then utilizes one of the flows to authenticate themselves, get the access token and then invoke the api.
You can use the Connected App from your production org, but to avoid the user hasn't approved this consumer error, I've found that you need to authenticate using the password and the Connected App's Client Id first. Then you'll be able to authenticate with JWT using the key.
You use OpenSSL for that. On Linux/macOS, a script like this will generate multiple certificates, if you need them (for multiple environments in a CI/CD context, for example).
if [ -z "$1" ]
echo "Missing #1 argument (password)."
echo "This script will output multiple certificates (canary, uat and production)."
Now, I want to remove dependency of Connected App because of some reasons. So I want to know is there any way to get new access token without using Connected App?
No. You will always need to provide the Client Id/Secret along with the refresh token to get the new access token. And for that purpose you will need your Connected App to be active. Take a look ...
The Saleforce CLI as you have it listed there no longer exists, and has been superseded by the newer CLI, which will be listed as the Force CLI instead. The first time you authenticate successfully, it will automatically be available in this list. To authenticate to a Sandbox, make sure you use the -r parameter:
sfdx force:auth:web:login -r https://test....
Marketing Cloud and Sales Cloud are 2 different instances, so even if you have integrated both the clouds, you need to login separately unless you have enabled Single sign on for both the clouds on your network.