James, the Postman as a proxy is something different than Postman using a proxy.

Rest client   -> Postman -> Rest service

Where Postman will record the traffic is Postman as a proxy. In this scenario 
the Rest client is will have to configure a proxy (Postman).

Best regards Niklas



[cid:[email protected]]
Niklas Uhrberg
Konsult
IT Development | Loans & Credit




Resurs Bank AB




Växel:  +46 42 38 20 00
E-post: [email protected]<mailto:[email protected]>
Webb:   www.resursbank.se<http://www.resursbank.se>




________________________________
From: James Dailey [[email protected]]
Sent: Tuesday, October 22, 2019 1:42 AM
To: Dev
Subject: Re: Record api traffic (Fineract 1.x)

Niklas - why can't you configure Postman to use Https through a proxy?  I'm not 
an expert on this, but it sounds counter-intuitive to me.
I found this link if applicable:
https://support.getpostman.com/hc/en-us/articles/360008893713-How-do-I-configure-Postman-to-work-through-a-proxy-

@jdailey67


On 2019/10/10 14:37:13, Niklas Uhrberg 
<[email protected]<mailto:[email protected]>> wrote:
> Hello!
>
> I have done some activities running Fineract 1.x and the community app 
> locally on my workstation.
>
> Now I would like to record a set of activities in order to create a quicker 
> way to jumpstart a simple setup . Say a loan product , a few clients with 
> their loans.
>
> (In the same way there are Postman scrips for Fineract CN)
>
> I have not done this before and my initial findings made me try running the 
> Community App -> Finract communication over HTTP (instead of HTTPS) . E.g. 
> Postman will require HTTP in proxy mode.
>
> I have not been able to pull this off.
> Have anyone of you done this kind of operation and can show the way to go 
> about this?
>
> Once I configure docker-compose to with the port mapping 8080:8080 I can at 
> least point my browser to fineract-provider, but the login screen (in the 
> community app) says:
> "Couldn't connect to server. Make sure you are using correct settings."
>
> I use the URL : 
> http://localhost/?baseApiUrl=http://localhost:8080&tenantIdentifier=default#/
>
> (And I have indeed verifed that I can login using the standard: 
> http://localhost/?baseApiUrl=https://localhost:8443&tenantIdentifier=default )
>
> Best regards Niklas
>
>

Reply via email to