OAuth issues on server behind firewall - ok with localhost

[Stuart Eastland]

I have been working on using the API running on a development machine with our website and oAuth callback on localhost.

Just installed on our server which is running inside a fire wall and now get www.sageone.com refused to connect   when trying to fetch the oauth token.  I am using an internal ip address.  Is this going to be possible?  I figured that localhost was also local so a local ip address should work too.

[Stuart Eastland]

In answer to my own question, I clearly need to use an SSL secured url that can be resolved externally so I need to get an SSL certificate installed on the server as my next step.

[Ben Smith]

Thanks for updating that Stuart. I've been trying to establish the steps I'd go through if doing the same. Glad you have got moved forward

 

Ben

[sylvain BECK]

Hi Stuart, Ben,

on the development server everything works perfectly

our server uses an SSL certificate. And, indeed, to access the call adress, you must provide (I think) the login and password for the SSL certificate.

Because, for the moment, I have the error message : Authorise Application Error, after having indicated the login and password of the sage account.

How did you specify these settings, because I can't find a place to do it in the dev console

Thanks for your help

Sylvain

[sylvain BECK]

I have a solution, I can add the login and password in the callback URL : https://login:password@URLcallBack

But I cannot add this URL in the developer console ...

have you maybe a solution ??