Hi Thorsten,
You generally have two patterns depending on the API:
Use:
OAuth2 Account → to obtain access token
HTTP Client snap→ to call API with mTLS
=> In this case:
OAuth token is fetched separately
mTLS is configured on the HTTP transport (Snap)
Option B (if OAuth endpoint itself requires mTLS)
This is the tricky case.
SnapLogic’s SSL OAuth2 Account documentation does NOT explicitely mentions support for true mTLS nor describe any mTLS OAuth flow (though you can give it a try).
=> There is a workaround:
Use a REST Snap with client cert configured
Call the token endpoint manually
Store/access token dynamically (e.g., pipeline parameter or cache)
