This message was deleted.
# citrix-netscaler
s
This message was deleted.
c
Switching to Kerberos gets pretty hairy thanks to having to setup KCD on everything to avoid double logins. I wonder if FAS might get around this requirement in a more elegant way.
d
so stepping back a bit. Whats the simplest way to tell Netscaler to talk to AD using Kerberos instead of NTLM? Or is that not possible?
I see that session policies have an entry for KCD account
c
Telling NS to talk to AD over Kerberos isn't generally an issue, but it's the delegation to other services that gets annoying. Last time I went down this road (which, granted, was years back) you had to setup KCD to storefront as well as any VDA the users could possibly hit, otherwise there would be multiple login prompts.
d
What about management interface on NS itself?
any possibility to tell LDAP policy / server to use Kerberos that you know of?
c
Haven't tried, but you might be able to get that to work by binding a Kerberos policy globally.
d
do you know if there are any documents around this? tbh this is going over my head a bit.
c
Unfortunately I haven't had the need to look recently. This one is a bit dated but should explain the pieces pretty well https://support.citrix.com/article/CTX135587
m
What do you have that’s doing NTLM? If you’ve setup LDAP on the gateway it should be doing kerberos impersonation I thought
d
It does not. As soon as I add a user to protected users they cant login to either management interface or the portal
I think you need to tell NS to use kerberos impersonation and I see documents around it but none of them are very clear to me and they are all different.
m
you can’t do impersonation with the protected users group though?
d
that I do not know
m
isn’t that the whole point of that group?
to turn off caching
d
yes it is
so what are my options?
m
I don’t know, I’ve never had to deal with anyone using that group
m
Maybe you can delegate auth to StoreFront: https://support.citrix.com/article/CTX223838
m
it looks like they can still be delegated, so I guess you need to go down the delegation path and make sure the accounts don’t have the sensitive flag checked which disables delegation
you could do constrained delegation with cert based auth, or SAML
like Okta
you’d need FAS
d
We have SAML/FAS in one of the environments. But that does not cover all the accounts. Also does not address the management logon
So I saw this article about KCD
m
You’d need to front the management interface with AAA, it doesn’t support that by default
d
So create AAA for ldap or something and use it as a server?
m
yes, I’ve never done it so I’m not sure if you can front the management gui with AAA, but that’s the only thing I can think of
d
ok that makes sense. I will see what I can dig up. Seems like a common issue people would have... Anyhow on that KCD article. Do I just create an AD account and add it to Session policy for storefront
?
session profile rather
m
I haven’t ever done it
d
🙂
me neither and info on creating those accounts and keytab file is... well maybe im slow
lol
m
I’ve never run into a situation where impersonation wouldn’t work
yeah, it look complicated
d
yea, this is a bit of special case situation
I just checked, KCD is not going to work with protected users