Skip to content

Commit d5b94f9

Browse files
authored
docs(connection): include WARNING message in the Username and Password Login (OAuth2 Resource Owner Password Credential) section (#15)
1 parent 3481190 commit d5b94f9

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

src/partials/document-v1/connection.html.md

+3
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,9 @@ conn.login(username, password, function(err, userInfo) {
5757
});
5858
```
5959

60+
> [!WARNING]
61+
> If you create your org in Summer ’23 or later, the OAuth 2.0 username-password flow is blocked by default as described in this [article](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_username-password_flow_blocked_by_default.htm&release=244&type=5). The username-password flow presents security risks. We recommend using the OAuth 2.0 client credentials flow instead.
62+
6063
### Session ID
6164

6265
If Salesforce session ID and its server URL information is passed from Salesforce (from 'Custom Link' or something),

src/partials/document/connection.html.md

+3
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,9 @@ console.log("User ID: " + userInfo.id);
4949
console.log("Org ID: " + userInfo.organizationId);
5050
```
5151

52+
> [!WARNING]
53+
> If you create your org in Summer ’23 or later, the OAuth 2.0 username-password flow is blocked by default as described in this [article](https://help.salesforce.com/s/articleView?id=release-notes.rn_security_username-password_flow_blocked_by_default.htm&release=244&type=5). The username-password flow presents security risks. We recommend using the OAuth 2.0 client credentials flow instead.
54+
5255
### Session ID
5356

5457
If you have a Salesforce session ID and its server URL information use it to authenticate.

0 commit comments

Comments
 (0)