Hi ​@Remco Kort, thanks for the explanation.

Could you perhaps give an example with tips for setting up a web connection with which a user table in the end application database can be synchronized with the user table in the IAM database? Just one way, from IAM DB to End App DB.

Is it possible to work with relative endpoints?

Which authentication settings ensure a secure connection?

​@Harm Horstman I would set that up the following way:

1. Create a webconnection, base url points to the base endpoint for indicium of the dev environment (for example: http://localhost/indicium/iam/iam/)
2. Auth type is going to depend on an API per API base, where possible I tend to use OAUTH, but in certain scenarios (especially if you are also using IP whitelisting) basic might be acceptable. If you are on a recent version of the software factory you could also consider using a PAT token, but these aren't really meant for server to server communication.
3. Create an endpoint that has 'usr’ as its path, 'usr’ is the iam view that has all the user data.
4. Set up an output parameter to store the json body. 
5. Make a process (system) flow to retrieve the data and parse it.
6. Change the base url of your webconnection in your various IAM's (dev, test, acc, prod) to point to the different IAM's for those environments. As far as i know webconnections will always connect to an absolute path, but by changing the base url in IAM you can point a web connection to a different iam without having to change anything in the software factory.

​@Remco Kort Great video, thanks for sharing! 

@Community: Please know that we also updated the Web connections documentation yesterday, we included more guidance and Use Cases to get you going: Web connections | Thinkwise Documentation