Firefox/Chrome/Edge NTLM SupportFirefox/Chrome/Edge NTLM Supporthttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1128663732024-03-29T12:21:43Z2024-03-29T12:21:43ZFirefox/Chrome/Edge NTLM SupportChristoph Rabelhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1128663722019-03-23T07:36:47Z2019-03-23T07:36:47Z<html><head></head><body>NTLM support for Firefox and Chrome is a frequently asked thing in the forum and also a frequent wish from my customers.<br>For a couple of years now NTLM works perfectly fine with Firefox and Chrome, but Liferay locks them out. That code here even locks out Edge.<br><br>https://github.com/liferay/liferay-portal/blob/7.2.x/modules/apps/portal-security-sso-ntlm/portal-security-sso-ntlm-impl/src/main/java/com/liferay/portal/security/sso/ntlm/internal/servlet/filter/NtlmFilter.java<br><br><pre><code>
@Override
public boolean isFilterEnabled(
HttpServletRequest request, HttpServletResponse response) {
if (!_browserSniffer.[b]isIe[/b](request)) {
return false;
}</code></pre><br>I believe, the best solution here would be to allow me to add my own filter condition code. Should be easily doable using OSGI. Adding a configuration is a bit complicated, because it still won't fill all Edge cases.<br><br><br>Instead of browserSniffer.isIE please add a new service and call something like:<br><br> if (!ntlmChecker.isNTLMEnabled(request)) { return false; }<br><br>Of course, I should be able to add my own ntlmChecker service, overriding the normal one.<br>This would allow me not only to check for browsers, but also for other flags or for subnets. I could enable NTLM in the intranet and disable it when a request comes from outside.</body></