Forum Discussion
Longhi_Mauro_19
Nimbostratus
NimbostratusReplace Microsoft NLB with BIGIP 2200S
Goodmorning,
I'm trying to replace serveral Microsoft NLB Cluster with a couple of BIGIP 2200S to do loadbalancing for different services.
I have configured management interfaces,upgraded a...
Kevin_Stewart
Employee
EmployeeClient side Kerberos will produce a single (useful) session variable: session.logon.last.username, which will be in UPN format. Example:
user@DOMAIN.COM
Kerberos SSO requires two input session variables: session.sso.token.last.username and session.logon.last.domain. That means in order to do client side and server side Kerberos together, you need a variable assignment in your access policy that splits the incoming UPN into separate username and domain values. So something like this:
session.sso.token.last.username = return [lindex [split [mcget {session.logon.last.username}] "@"] 0]
session.logon.last.domain = return [lindex [split [mcget {session.logon.last.username}] "@"] 1]
