Skip to content
Notifications
Clear all

Anyone running Appgate SDP with Okta or Azure AD auth?

4 Posts
4 Users
0 Reactions
53 Views
(@andrewh)
Reputable Member
Joined: 4 months ago
Posts: 363
Topic starter   [#23861]

Hey everyone, new here and still learning the ropes with SDP.

We're setting up Appgate SDP and need to use our existing identity provider. Does anyone have experience integrating it with Okta or Azure AD for user authentication? I'm curious about the setup steps and if there are any common pitfalls to watch out for. Our team mainly uses Azure AD, but Okta is also an option for us.

Thanks for any pointers you can share! 😊



   
Quote
 danf
(@danf)
Estimable Member
Joined: 4 months ago
Posts: 168
 

Both work, but Azure AD's setup is a bit more straightforward if you're already in that ecosystem. The real catch isn't the initial handshake, it's the group synchronization for policies later on. That's where most people get tripped up.

You'll see a lot of glowing reviews online, but ignore anyone who says it's flawless after a week. Talk to me in six months when you've had to update claims or change provisioning rules. That's when the real, grumpy feedback comes out.


Anecdotes aren't data.


   
ReplyQuote
 amym
(@amym)
Trusted Member
Joined: 4 months ago
Posts: 85
 

Yeah, I'm looking into this exact setup right now. The documentation for Azure AD is pretty clear for the initial SAML connection, but I got stuck for a while on the attribute mapping for user claims. It seems like you have to be very precise about the attribute names you send from Azure, or the Appgate side just won't recognize them for policy assignment.

Have you figured out yet how you're planning to handle device context or conditional access from the identity provider side? That's the next hurdle I'm trying to understand.



   
ReplyQuote
(@gardener42)
Reputable Member
Joined: 4 months ago
Posts: 391
 

Both Azure AD and Okta are viable, but your choice should hinge on what you need beyond basic SAML auth. Azure AD's integration is indeed more documented if you're already using Microsoft services, but Okta offers more granularity in session policies and custom attributes out of the box, which can be crucial for dynamic policy mapping in Appgate.

The initial configuration is fairly standard. The more complex piece is designing a reliable attribute flow for group memberships and user claims that Appgate's policy engine can consume. You'll need to map attributes like `memberOf` or a custom claim to Appgate's expected `entitlement` format. A common oversight is not accounting for nested group resolution; neither IdP passes nested groups by default in SAML assertions, so you often need to flatten that structure beforehand.

For your POC, I'd recommend setting up a small test population in both, focusing on the policy trigger conditions. See which IdP allows you to more cleanly pass the specific `nameid` format and group attributes your security team will use for access rules. The pitfalls aren't in the connection itself, but in maintaining that mapping as your directory schema evolves.



   
ReplyQuote