Changes related to better README file #47
Conversation
|
@glang @pmedapuram @vamshi-sfdc Can two of you please review? |
| - Please verify the oauth setup for the org by executing the following command : | ||
| ```shell | ||
| curl -v <Salesforce_Org_URL>/services/oauth2/token -d "grant_type=password" -d "client_id=****************" -d "client_secret= **************" -d "username=***********" -d "password= *******" | ||
| curl -v <Salesforce_Org_URL>/services/oauth2/token -d "grant_type=password" -d "client_id=*CLIENT_ID_GOES_HERE*" -d "client_secret= *CLIENT_SECRET_GOES_HERE*" -d "username=*yourusername@yourdomain.com*" -d "password= *your_password_goes_here+*" |
There was a problem hiding this comment.
should this be a encrypted/encoded password?
provide pointers on how encoding should be done?
does it hurt if you ask all users to use a encoded password?
|
I am currently looking over it and will send you a version of this with some minor grammatical corrections, if you don't mind :) |
|
sure |
|
@adarsh-ramakrishna-sfdc @vamshi-sfdc Here is an edited version of the README I made: https://gist.github.com/glang/d1059308e0688b24b0259c150e73f4ae This was mainly a grammar focused edit, and not a content changing edit. There only content change was regarding the security token appended to the password, in which I provided more details about. |
|
@glang can you send a pull request to see this diff? |
|
Looks like lot of changes have happened since the time this PR was created, resulting in merge conflicts. I suggest we close this PR and work on documentation after we resolve issues on namespace handling, We will have the reference of this PR anyway. |
|
@glang please resolve this PR |
|
@vamshi-sfdc Sure, though it's been quite a while since I've worked on this so I'll need to spend some time walking through it. |
No description provided.