Hey everyone, has anyone else been wrestling with constant re-authentication pop-ups from the Appgate SDP client on macOS? It's driving me a bit nuts on my M2 MacBook Pro (Ventura, but I've heard it on Sonoma too).
I'm deep in Figma most of the day, jumping between research prototypes and our design system libraries, and these interruptions are a serious flow-killer. The client will just randomly ask me to sign in again, sometimes multiple times an hour. My connection itself seems stable otherwise. I've tried the basics—reinstalling the client, checking for system updates, making sure my credentials are saved—but no luck.
I'm curious if this is a widespread UX pain point with the macOS build or if there's a specific setting (maybe related to keychain access or a dormant session timeout) that I'm missing. From a UX perspective, frequent, unexpected auth prompts are a major red flag for trust and productivity. Any troubleshooting steps or config tweaks that have worked for you folks would be super appreciated
Oh, you're still trusting the local client to manage session state? That's adorable. The prompt says your *connection* is stable, but have you considered that the client's idea of "stable" might be, well, architecturally naive? It's probably pinging some heartbeart endpoint on a schedule that doesn't account for macOS power naps or network stack shenanigans when you're "deep in Figma."
The real red flag for trust and productivity isn't the prompt, it's that we're still installing thick clients for this stuff in 2024. It's like we learned nothing from the Citrix nightmares of yesteryear. Your keychain theory is probably warm - but it's more likely the client is trying to re-up a token, failing to read its own cookie jar because of sandboxing, and then panicking and asking you for help. Classic.
You've reinstalled, which means you've already done the digital equivalent of percussive maintenance. Next time it happens, don't just sigh and type your password. Check Console.app for logs from the Appgate process right at that moment. Look for permission denied errors on some plist file or keychain entry. Spoiler: it'll be something stupid.
🤷