Fix CSV format issue and add additional details about authenticating against Bitly

README.md

@@ -37,8 +37,8 @@ To use validating a secret as an access token against the bitly API, use the fol
 The datafile is a csv format like this.
 
 ```
-login,ip,tls,topic,channel,subscribe,publish
-johndoe,127.0.0.1,both,test_topic,test_channnel,subscribe,
+login,ip,tls_required,topic,channel,subscribe,publish
+johndoe,127.0.0.1,true,test_topic,test_channnel,subscribe,
 ```
 
 Typical usage will be like this:
@@ -50,3 +50,29 @@ Typical usage will be like this:
       --oauth2-echo-endpoint=https://api-ssl.bitly.com/v3/user/info \
       --oauth2-response-path=data.login
 
+#### Authenticating against the Bitly API
+
+Get your access token here:
+[https://bitly.com/a/oauth_apps](https://bitly.com/a/oauth_apps)
+
+Permissions.csv:
+```
+login,ip,tls_required,topic,channel,subscribe,publish
+<your bitly username>,127.0.0.1,true,test_topic,test_channnel,subscribe,publish
+```
+> TLS is required. Your username can both subscribe and publish.
+
+Starting nsqd:
+```
+nsqd -tls-cert=cert.pem -tls-key=key.pem -auth-http-address=127.0.0.1:4181
+```
+
+Starting `pynsqdauthd`:
+```
+python pynsqauthd.py \
+  --data_file=permissions.csv \
+  --http_address=0.0.0.0:4181 \
+  --ttl=3600 \
+  --oauth2-echo-endpoint=https://api-ssl.bitly.com/v3/user/info \
+  --oauth2-response-path=data.login
+```