These are chat archives for ushahidi/Community

10th
Jul 2017
lorinivalerio
@lorinivalerio
Jul 10 2017 13:00
Hi guys, I am trying to setup V3 on a dedicated server, I setup a vagrant machine for platform-api which i can access and where i get response from when using curl and I cloned the platform-client on the dedicated server. Everything seems fine. Got only an error when running vagrant up && vagrant provision , err: Update composer: composer already up to date. Everything seems up and running but when i try to access the web interface It hangs (or i get 'try reloading the page'). 95.110.227.227:8081
azizfall
@azizfall
Jul 10 2017 18:33
ok so I found some documentation for the ushahidi v3 API under platform/docs/api/ the only problem now is that I am trying to get an access token by following the instructions in platform/docs/api/auth.apib
but the URL http://192.168.33.110/api/v3/oauth/token results in a 404 error for me, and I am also not entirely sure how to interpret the json post request under the documentation, can anyone help me with this problem
@rjmackay would you be able to help me with my problem? I see the documentation under your name
Ushbot
@ushbot
Jul 10 2017 21:38
[Robbie Mackay, Ushahidi] @azizfall the oauth/token endpoint doesn't have a api/v3 prefix. I think the docs get that wrong. So just http://192.168.33.110/oauth/token
[Robbie Mackay, Ushahidi] You can see the rendered API docs here: http://preview.ushahidi.com/platform/develop/api/index.html
azizfall
@azizfall
Jul 10 2017 22:31
thank you very much @rjmackay
azizfall
@azizfall
Jul 10 2017 22:38
but how do I obtain a client id, I am currently the admin of my deployment
Ushbot
@ushbot
Jul 10 2017 22:40
[Robbie Mackay, Ushahidi] There should be a default client ushahidiui in the DB already
[Robbie Mackay, Ushahidi] You can generally just use that, since the client id + secret don't gain you any elevated access, unless you also authorize with a username + password
azizfall
@azizfall
Jul 10 2017 22:43
oh its just that the client_id and client_secret are parameters in the post request to obtain an access, token so can I safely omit that from the json post
or am I going wrong somewhere?
azizfall
@azizfall
Jul 10 2017 22:51
ok I think I got it, I just looked under the table oauth_clients, and I saw the client id and secret
thanks again for all the help