Your first problem is that Java is supposed to be "write-once/run-anywhere". So there can by definition be no Windows security services except by escaping via JNI.
Additionally an HTTP server and an NFS (LAN server) have only 2 things in common. 1) they both work using network hardware 2) they have the
word "server" in their name. Any computer with a network card in it can be an HTTP server, whether the word "Server" appears in its OS name or not. In fact, I think you might even find HTTP servers for DOS!
What you really want, I think, is to try apply the security tokens granted by logging in as user X on domain Y to provide some sort of guidelines on what services and features the HTTP server will grant the user. That's not always as straightforward as it seems. Only in the case where you're using HTTP as a glorified file server is there a direct correspondence.
Most people who ask this kind of question really want merely to avoid a second-level signon, so what they are really looking for is a way to determine the user's identify. There are some products out there to help with that
You might also want to search the local servlet and
JSP forums and see what others have had to say on the topic.