Marwen M.

Hi Thorsten, You generally have two patterns depending on the API:

Use:

=> In this case:

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:

You're welcome!

Hi Tom, What you’re trying to achieve is correct in principle, but the behavior you’re seeing usually comes from how permissions are combined across project spaces in SnapLogic. Permissions are additive, meaning a user can end up with higher privileges if they inherit them from another role, group, or parent project space. So even if you explicitly grant “Read & Execute” on the target project space, users can still edit pipelines if they also have: “Write” or “Full Access” on the same project space (via another group), or

What to check

Direct vs inherited permissions : Even if “Read & Execute” is set locally, inherited permissions can override your intention (Propagate permission check box, if you're using project folders).