| 00:22.58 | *** join/#asterisk-dev tzafrir (~tzafrir@bzq-218-28-58.cablep.bezeqint.net) |
| 00:22.58 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 00:28.15 | *** join/#asterisk-dev serafie (~erin@user-24-214-173-250.knology.net) |
| 00:34.19 | *** join/#asterisk-dev serafie (~erin@user-24-214-173-250.knology.net) |
| 01:31.31 | *** join/#asterisk-dev serafie (~erin@user-24-214-173-250.knology.net) |
| 02:37.30 | *** join/#asterisk-dev serafie (~erin@user-24-214-173-250.knology.net) |
| 02:50.22 | *** join/#asterisk-dev italorossi (~italoross@67.201.69.130) |
| 04:17.51 | *** join/#asterisk-dev italorossi (~italoross@67.201.69.130) |
| 04:54.12 | *** join/#asterisk-dev italorossi (~italoross@67.201.69.130) |
| 05:21.01 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.127.74) |
| 05:25.19 | *** join/#asterisk-dev italorossi (~italoross@67.201.69.130) |
| 05:57.19 | *** join/#asterisk-dev italorossi (~italoross@67.201.69.130) |
| 06:11.33 | *** join/#asterisk-dev italorossi (~italoross@67.201.69.130) |
| 06:49.02 | *** join/#asterisk-dev oron (~oron_lapt@line25-214.adsl.actcom.co.il) |
| 07:58.02 | *** join/#asterisk-dev vlad_starkov (~vlad_star@194.154.71.230) |
| 08:34.42 | *** join/#asterisk-dev bulkorok (~chatzilla@85.183.61.47) |
| 22:05.00 | *** join/#asterisk-dev infobot (~infobot@rikers.org) |
| 22:05.00 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk |
| 22:26.15 | pabelanger | Success! CLI client working with Asterisk ARI |
| 22:26.16 | pabelanger | :D |
| 22:26.22 | pabelanger | just using basic auth for now |
| 22:29.11 | pabelanger | no dlee today? |
| 22:31.52 | *** part/#asterisk-dev kharwell (~kharwell@nat/digium/x-rjydyqzbnfhymwzb) |
| 22:31.53 | jrose_atDigium | pabelanger: dlee left a little early today. |
| 22:32.17 | jrose_atDigium | He said he may or may not be back at some point. |
| 22:32.42 | pabelanger | jrose_atDigium, going to hit him up on twitter :D |
| 22:33.00 | *** join/#asterisk-dev serafie (~erin@user-24-214-173-250.knology.net) |
| 23:01.07 | pabelanger | Is there any information how authentication for ARI works? |
| 23:01.40 | pabelanger | I am confused with basic and crypto password_format |
| 23:01.51 | pabelanger | if I am reading this right, one is just using Basic auth |
| 23:01.56 | pabelanger | the other uses curl -i -X GET -H 'Content-Type: application/json' -H 'User-Agent: sarlacc' http://localhost:8088/ari/asterisk/info?api_key=username:password |
| 23:02.34 | pabelanger | which basically still transmitting the password in plain text |
| 23:03.46 | jrose_atDigium | You might have to wait for Dlee on that one. |
| 23:05.04 | pabelanger | Also, what does: type=user represent in ari.conf |
| 23:05.26 | pabelanger | Different levels of security for the API? |
| 23:07.19 | jrose_atDigium | Nah, I think that's more of planning for the future when there are object types that can be specified in ari.conf other than users and the general section. |
| 23:10.26 | Juggie | pabelanger, unless there is some sort of challenge/response system |
| 23:10.29 | Juggie | its gonna remain clear text |
| 23:11.52 | Juggie | it does only BA and auth via query string |
| 23:12.00 | Juggie | so it would appear to not have any encryption |
| 23:16.44 | pabelanger | Juggie, Ya, I guess that is what I asking. Something like oauth 2.0 |
| 23:17.23 | *** join/#asterisk-dev w9sh (~sph@50-79-224-193-static.hfc.comcastbusiness.net) |
| 23:17.25 | Juggie | yeah... |
| 23:18.09 | Juggie | as i said in other chan, typically you see rest type services returning you a key which you then use as the seed for an encryption with your password, the rest/api would then return you a key for the session which you would tack into every request. |
| 23:19.31 | Juggie | in all likely hood though you would be firewalling this type of service and only permittting specific clients |
| 23:46.43 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.124.155) |