@salesforce/plugin-auth 3.0.14 → 3.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -322,6 +322,7 @@
322
322
  "auth:device:login"
323
323
  ],
324
324
  "args": {},
325
+ "deprecateAliases": true,
325
326
  "description": "Use this command to allow a device to connect to an org.\n\nWhen you run this command, it first displays an 8-digit device code and the URL for verifying the code on your org. The default instance URL is https://login.salesforce.com, so if the org you're authorizing is on a different instance, use the --instance-url. The command waits while you complete the verification. Open a browser and navigate to the displayed verification URL, enter the code, then click Connect. If you aren't already logged into your org, log in, and then you're prompted to allow the device to connect to the org. After you successfully authorize the org, you can close the browser window.",
326
327
  "examples": [
327
328
  "Authorize an org using a device code, give the org the alias TestOrg1, and set it as your default Dev Hub org:\n<%= config.bin %> <%= command.id %> --set-default-dev-hub --alias TestOrg1",
@@ -481,9 +482,10 @@
481
482
  "auth:jwt:grant"
482
483
  ],
483
484
  "args": {},
485
+ "deprecateAliases": true,
484
486
  "description": "Use this command in automated environments where you can’t interactively log in with a browser, such as in CI/CD scripts.\n\nLogging into an org authorizes the CLI to run other commands that connect to that org, such as deploying or retrieving a project. You can log into many types of orgs, such as sandboxes, Dev Hubs, Env Hubs, production orgs, and scratch orgs.\n\nComplete these steps before you run this command:\n\n 1. Create a digital certificate (also called digital signature) and the private key to sign the certificate. You can use your own key and certificate issued by a certification authority. Or use OpenSSL to create a key and a self-signed digital certificate.\n 2. Store the private key in a file on your computer. When you run this command, you set the --jwt-key-file flag to this file.\n 3. Create a custom connected app in your org using the digital certificate. Make note of the consumer key (also called client id) that’s generated for you. Be sure the username of the user logging in is approved to use the connected app. When you run this command, you set the --client-id flag to the consumer key.\n\nSee https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_jwt_flow.htm for more information.\n\nWe recommend that you set an alias when you log into an org. Aliases make it easy to later reference this org when running commands that require it. If you don’t set an alias, you use the username that you specified when you logged in to the org. If you run multiple commands that reference the same org, consider setting the org as your default. Use --set-default for your default scratch org or sandbox, or --set-default-dev-hub for your default Dev Hub.",
485
487
  "examples": [
486
- "Log into an org with username jdoe@example.org and on the default instance URL (https://login.salesforce.org). The private key is stored in the file /Users/jdoe/JWT/server.key and the command uses the connected app with consumer key (client id) 04580y4051234051.\n<%= config.bin %> <%= command.id %> --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id 04580y4051234051",
488
+ "Log into an org with username jdoe@example.org and on the default instance URL (https://login.salesforce.com). The private key is stored in the file /Users/jdoe/JWT/server.key and the command uses the connected app with consumer key (client id) 04580y4051234051.\n<%= config.bin %> <%= command.id %> --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id 04580y4051234051",
487
489
  "Set the org as the default and give it an alias:\n<%= config.bin %> <%= command.id %> --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id 04580y4051234051 --alias ci-org --set-default",
488
490
  "Set the org as the default Dev Hub and give it an alias:\n<%= config.bin %> <%= command.id %> --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id 04580y4051234051 --alias ci-dev-hub --set-default-dev-hub",
489
491
  "Log in to a sandbox using URL https://MyDomainName--SandboxName.sandbox.my.salesforce.com:\n<%= config.bin %> <%= command.id %> --username jdoe@example.org --jwt-key-file /Users/jdoe/JWT/server.key --client-id 04580y4051234051 --alias ci-org --set-default --instance-url https://MyDomainName--SandboxName.sandbox.my.salesforce.com"
@@ -673,6 +675,7 @@
673
675
  "auth:sfdxurl:store"
674
676
  ],
675
677
  "args": {},
678
+ "deprecateAliases": true,
676
679
  "description": "The Salesforce DX (SFDX) authorization URL must have the format \"force://<clientId>:<clientSecret>:<refreshToken>@<instanceUrl>\". NOTE: The SFDX authorization URL uses the \"force\" protocol, and not \"http\" or \"https\". Also, the \"instanceUrl\" inside the SFDX authorization URL doesn't include the protocol (\"https://\").\n\nYou have three options when creating the authorization file. The easiest option is to redirect the output of the \"<%= config.bin %> org display --verbose --json\" command into a file. For example, using an org with alias my-org that you've already authorized:\n\n $ <%= config.bin %> org display --target-org my-org --verbose --json > authFile.json\n\nThe resulting JSON file contains the URL in the \"sfdxAuthUrl\" property of the \"result\" object. You can then reference the file when running this command:\n\n $ <%= config.bin %> <%= command.id %> --sfdx-url-file authFile.json\n\nNOTE: The \"<%= config.bin %> org display --verbose\" command displays the refresh token only for orgs authorized with the web server flow, and not the JWT bearer flow.\n\nYou can also create a JSON file that has a top-level property named sfdxAuthUrl whose value is the authorization URL. Finally, you can create a normal text file that includes just the URL and nothing else.",
677
680
  "examples": [
678
681
  "Authorize an org using the SFDX authorization URL in the files/authFile.json file:\n<%= config.bin %> <%= command.id %> --sfdx-url-file files/authFile.json",
@@ -1007,5 +1010,5 @@
1007
1010
  ]
1008
1011
  }
1009
1012
  },
1010
- "version": "3.0.14"
1013
+ "version": "3.1.0"
1011
1014
  }
package/package.json CHANGED
@@ -1,25 +1,25 @@
1
1
  {
2
2
  "name": "@salesforce/plugin-auth",
3
3
  "description": "plugin for sf auth commands",
4
- "version": "3.0.14",
4
+ "version": "3.1.0",
5
5
  "author": "Salesforce",
6
6
  "bugs": "https://github.com/forcedotcom/cli/issues",
7
7
  "dependencies": {
8
8
  "@oclif/core": "^3.15.0",
9
- "@salesforce/core": "^6.4.0",
9
+ "@salesforce/core": "^6.4.2",
10
10
  "@salesforce/kit": "^3.0.15",
11
- "@salesforce/sf-plugins-core": "^5.0.12",
11
+ "@salesforce/sf-plugins-core": "^5.0.13",
12
12
  "@salesforce/ts-types": "^2.0.9",
13
13
  "chalk": "^5.3.0",
14
14
  "open": "^9.1.0"
15
15
  },
16
16
  "devDependencies": {
17
- "@oclif/plugin-command-snapshot": "^5.0.3",
18
- "@salesforce/cli-plugins-testkit": "^5.1.2",
19
- "@salesforce/dev-scripts": "^8.1.2",
20
- "@salesforce/plugin-command-reference": "^3.0.56",
17
+ "@oclif/plugin-command-snapshot": "^5.0.5",
18
+ "@salesforce/cli-plugins-testkit": "^5.1.3",
19
+ "@salesforce/dev-scripts": "^8.2.0",
20
+ "@salesforce/plugin-command-reference": "^3.0.58",
21
21
  "@salesforce/ts-sinon": "^1.4.19",
22
- "eslint-plugin-sf-plugin": "^1.16.15",
22
+ "eslint-plugin-sf-plugin": "^1.17.0",
23
23
  "oclif": "^4.1.0",
24
24
  "shx": "0.3.4",
25
25
  "ts-node": "^10.9.2",
@@ -219,7 +219,7 @@
219
219
  "output": []
220
220
  },
221
221
  "link-check": {
222
- "command": "node -e \"process.exit(process.env.CI ? 0 : 1)\" || linkinator \"**/*.md\" --skip \"CHANGELOG.md|node_modules|test/|confluence.internal.salesforce.com|%s\" --markdown --retry --directory-listing --verbosity error",
222
+ "command": "node -e \"process.exit(process.env.CI ? 0 : 1)\" || linkinator \"**/*.md\" --skip \"CHANGELOG.md|node_modules|test/|confluence.internal.salesforce.com|my.salesforce.com|%s\" --markdown --retry --directory-listing --verbosity error",
223
223
  "files": [
224
224
  "./*.md",
225
225
  "./!(CHANGELOG).md",
@@ -231,7 +231,7 @@
231
231
  "exports": "./lib/index.js",
232
232
  "type": "module",
233
233
  "sfdx": {
234
- "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-auth/3.0.14.crt",
235
- "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-auth/3.0.14.sig"
234
+ "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-auth/3.1.0.crt",
235
+ "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-auth/3.1.0.sig"
236
236
  }
237
237
  }