Abhinandan Kunne Posted March 21, 2019 Share Posted March 21, 2019 Hi, We have email solution hosted in our NetScaler but authentication not doing via NetScaler. It is happening on exchange level. We are seen some legitimate user name and host are trying to access our external exchange environment. Now if netScaler will do authentication proxy on behalf of exchange we can block this access via pattern set and responder policy. However, in current architecture can we block user name or host name by any chance. Thanks in advance. Link to comment Share on other sites More sharing options...
Raman Kaushik Posted March 21, 2019 Share Posted March 21, 2019 You can use a responder policy on you LB vserver to check for hostname and use action as drop or reject Link to comment Share on other sites More sharing options...
Diego Oliveira Posted March 21, 2019 Share Posted March 21, 2019 As Raman said, you can use policies. See some e.g: https://support.citrix.com/article/CTX222249 https://support.citrix.com/article/CTX207018 Link to comment Share on other sites More sharing options...
Abhinandan Kunne Posted March 21, 2019 Author Share Posted March 21, 2019 Thanks for your response... We are not sure about source IP, we have only user name and host name information...can any way we can block it by user name or host name in NetScaler for this email communication???? Please note, NetScaler is not doing any authentication proxy for email and user authentication happening from exchange server level. Thank You. Link to comment Share on other sites More sharing options...
Mathieu BRUSTON1709159739 Posted March 27, 2019 Share Posted March 27, 2019 Hello the authorization side can be made only with a AAA function. So you have to add the netscaler as authentication proxy. if the authentication could be a probleme, perhaps you can just create an ldap action without authentication only to get the user and perform action after. Regards, Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.