This message was deleted.
# citrix-netscaler
s
This message was deleted.
m
Have you taken a look at the step-up authentication docs? https://docs.citrix.com/en-us/citrix-adc/current-release/aaa-tm/configure-login-mechanism-authentication.html I haven't tried it with a gateway, but i assume it should work still
d
I'll have a look, thanks for that sir. Does that mean my observation is expected behaviour?
m
If they are seen as the same authentication level, then i would assume the gateway would just accept the already know credentials
c
If you want to prevent that behavior you can likely edit the authentication cookie domain so it's not matching both OWA and GW domain names. Under the hood AAA-TM and GW share authentication mechanisms, so if you have an active AAA session with the same authentication domain then that session will be valid for the gateway by default.
Step up auth can let you customize that behavior in a more granular fashion but yes what you're seeing is expected assuming the aaa-tm cookie domain covers the gateway domain as well.
d
And where is the authentication cookie domain set? Is it the SSO Domain in the Session Profile?
c
The authentication domain setting is on the AAA-TM virtual server for classic policies
d
Sorry for my stupidity, but I can't find it. We have a Advanced Auth Policy bound to the vServer.
c
Oh if you're already on advanced auth policies then you should be able to control that in the Authentication Profile
d
Found it. There is no Authentication Profile set up currently. So my last question: I have to create a profile and specify the Authentication Domain. But since it defaults to FQDN what should I set?
c
If you have separate profiles for gateway and OWA, then you should be able to put the OWA FQDN in there for the OWA profile. Standard disclaimer applies, always test first.
d
Gateway Auth is not done via AAA. Only OWA. So OWA FQDN should be safe. Thanks a lot for your help 🙂
👍 1
I need to get back in this thread again. I checked the cookie domain for OWA and Gateway and there are different domains set. Is this the wrong approch? IMO since there is no wildcard how is that cookie valid for another url?