Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Changes related to better README file #47

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

adarsh-ramakrishna-sfdc
Copy link
Contributor

No description provided.

@adarsh-ramakrishna-sfdc
Copy link
Contributor Author

@glang @pmedapuram @vamshi-sfdc Can two of you please review?

- http://salesforce.stackexchange.com/questions/40346/where-do-i-find-the-client-id-and-client-secret-of-an-existing-connected-app
- http://stackoverflow.com/questions/18464598/where-to-get-client-id-and-client-secret-of-salesforce-api-for-rails-3-2-11
- http://www.calvinfroedge.com/salesforce-how-to-generate-api-credentials/
- 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=*[email protected]*" -d "password= *your_password_goes_here+*"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

@glang
Copy link
Contributor

glang commented Jul 19, 2016

I am currently looking over it and will send you a version of this with some minor grammatical corrections, if you don't mind :)

@vamshi-sfdc
Copy link
Contributor

sure

@glang
Copy link
Contributor

glang commented Jul 19, 2016

@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.

@vamshi-sfdc
Copy link
Contributor

@glang can you send a pull request to see this diff?

@adarshramakrishna
Copy link
Collaborator

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.
@vamshi-sfdc @awillia2

@vamshi-sfdc
Copy link
Contributor

@glang please resolve this PR

@glang-sfdc
Copy link
Collaborator

@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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants