Hey everyone. New to the forum, but I've been using Absolute Secure Access (Claw) for a few months now.
We started rolling it out for our devs to access some internal tools. Lately, we're seeing random failures where our CI/CD pipelines (like Jenkins) can't talk to our artifact repos. Our admin says it's because Claw's certificate pinning is super strict and it's rejecting the internal CA we use for those systems. Is this a common thing? How are you all handling internal integrations without breaking them?
Yep, hit this exact issue with GitLab runners. The pinning can be a real headache for internal CAs. Our workaround was to push our internal CA cert to the trusted store on the CI agents, but even then, some requests from the Claw client would fail intermittently. We ended up having to make an exception list in the Claw policy for those specific internal endpoints. Talk to your admin about that path - it's not ideal, but it got our builds green again.