Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

ntlm authentication

Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I have been working in an application which is an intranet application which has been extended for domain compatibility as well as browser compliance.

Now some of the codes are not working in either of the two.

For browser compliance the code 64decoder is not working....
when changed to ntlm rewuest.getRemoteUser(), it wors fine in safari.
Then it will not work in a different domain.

I am using a custom filter for domain compliance.

But to address the mac safari issue, i have used the ntlmHttpFilter for the request.getRemoteUser() to work correctly.

But then we cannot have two flters in the web.xml file.

Now i want to know if we could write the custom filter in such a way that it uses the request.getRemoteUser() wiwthout looking for the ntlmHttpFilter.
Because if we do that, we cannot make compliant for both the issues.

I was thinking if the ntlmHttpFilter class could be used in the custom filter class without using the filter.

I would really appreciateit if anyone could come up witha solution.

THankss... :-)
I don't get it. A whale wearing overalls? How does that even work? It's like a tiny ad wearing overalls.
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic