summaryrefslogtreecommitdiff
path: root/configs
diff options
context:
space:
mode:
authorAndrey Egorov <andr06@gmail.com>2017-08-04 17:25:52 +0300
committerJoshua Colp <jcolp@digium.com>2017-08-15 11:08:59 +0000
commit54e3ac402ff167ba2463b386ea25fa5327be86c6 (patch)
tree706b2f874074c1008a32bb5499a22505eb1c9129 /configs
parent9bc114ffba6fe173876dcdb46a3d5f49c5d19d55 (diff)
res_xmpp: Google OAuth 2.0 protocol support for XMPP / Motif
Add ability to use tokens instead of passwords according to Google OAuth 2.0 protocol. ASTERISK-27169 Reported by: Andrey Egorov Tested by: Andrey Egorov Change-Id: I07f7052a502457ab55010a4d3686653b60f4c8db
Diffstat (limited to 'configs')
-rw-r--r--configs/samples/xmpp.conf.sample23
1 files changed, 23 insertions, 0 deletions
diff --git a/configs/samples/xmpp.conf.sample b/configs/samples/xmpp.conf.sample
index dad0f79ef..e3a4be142 100644
--- a/configs/samples/xmpp.conf.sample
+++ b/configs/samples/xmpp.conf.sample
@@ -18,6 +18,29 @@
;pubsub_node=pubsub.astjab.org ; Node to use for publishing events via PubSub
;username=asterisk@astjab.org/asterisk ; Username with optional resource.
;secret=blah ; Password
+;refresh_token=TOKEN_VALUE ; Refresh token issued by Google OAuth 2.0 protocol.
+ ; `secret` must NOT be set if you use OAuth.
+ ; See https://developers.google.com/identity/protocols/OAuth2WebServer
+ ; for more details.
+ ; For test reasons you can obtain one on the page
+ ; https://developers.google.com/oauthplayground/
+ ; 1. Click on Settings icon, check "Use your own OAuth credentials"
+ ; and enter your Client ID and Client Secret (see below).
+ ; 2. Input the scope https://www.googleapis.com/auth/googletalk
+ ; and push "Authorize APIs" button.
+ ; 3. Approve permissions.
+ ; 4. On section "Step 2" push "Exchange authorization code for tokens"
+ ; and get your Refresh token.
+;oauth_clientid=OAUTH_CLIENT_ID_VALUE ; The application's client id to authorize using Google OAuth 2.0 protocol.
+;oauth_secret=OAUTH_SECRET_VALUE ; The application's client secret to authorize using Google OAuth 2.0 protocol.
+ ; 1. Create new Project on the page:
+ ; https://console.cloud.google.com/apis/credentials/oauthclient
+ ; 2. Create new Application ID on the same page with type Web-application.
+ ; In section "Allowed URI redirections" put the path to the corresponding
+ ; script on your site or https://developers.google.com/oauthplayground
+ ; if you would like to obtain refresh_token from users by hand
+ ; (for example, for test reasons).
+ ; 3. Client ID and Client Secret will be shown and available on the same page.
;priority=1 ; Resource priority
;port=5222 ; Port to use defaults to 5222
;usetls=yes ; Use tls or not