After a bit of beating my head against a silly local configuration problem, this seems to be working well for me. It might be nice to do some kind of tool to generate the oauth stuff, or in the absense of that, some basic steps. It could even be the basic curl commands like:
1. curl --dump-header - -X POST --data 'oauth_consumer_key=airlinetest&oauth_signature_method=PLAINTEXT&oauth_signature=%26' https://launchpad.net/+request-token
After a bit of beating my head against a silly local configuration problem, this seems to be working well for me. It might be nice to do some kind of tool to generate the oauth stuff, or in the absense of that, some basic steps. It could even be the basic curl commands like: consumer_ key=airlinetest &oauth_ signature_ method= PLAINTEXT& oauth_signature =%26' https:/ /launchpad. net/+request- token
1. curl --dump-header - -X POST --data 'oauth_
2. copy the long string after 'oauth_token=' and go to: https:/ /launchpad. net/+authorize- token?oauth_ token={oauth_token} in a browser /launchpad. net/+authorize- token?oauth_ token={oauth_token}
https:/
3. Authorize read/write (no private data) in the web browser
4. Look at the long string above again, pull out the oauth token and oauth secret. Set the following environment vars...
I'm having problems where it looks like bsb doesn't actually use the oauth creds I provided it, but that doesn't appear to be related to this change.