Everyone has their master IdP (Entra ID, OKTA, Google Identity…) already in place anyways, so what’s all the fuzz about? It might be a bit more useful to walk-through a couple of examples to shed some light on the why. This post will explain three use-cases: One thing in common for all of the use-cases … NetScaler as IdP/SP – why?
Last one (for now); having SSO all the way to the application is critical for users and from security perspective. And most importantly; achievable with NetScaler. Overview In the example the web application acts as an OIDC SP, using NetScaler as an OIDC IdP. NetScaler authentication itself is similar to the previous post, so it’s … Chained federated authentication, NetScaler as SP and IdP
Second one – are you ready? I think this one is a bit more interesting and something you might run in to! Overview In the example the reverse proxy is protected with Microsoft Entra ID authentication capabilities. NetScaler is configured as SAML SP for Microsoft Entra ID and no SSO for the destination web front … Federated authentication, NetScaler as SP
Overview Far too often I’m facing an assumption that the NetScaler is “just a load balancer” or the Gateway for Citrix environments. Of course it’s true that NetScaler can do both of the above, but it’s capable of so much more. We here at Comping have been working on various cases around identity and NetScaler … NetScaler Identity handling capabilities
