GWT, jcifs, and multiple prompting for login?

I figured it out. I built the dummy servlet and then used a RequestBuilder on the client side to do a get on that servlet. That servlet then gets the userprincipal.

Here is the client side: RequestBuilder getNameRB = new RequestBuilder(RequestBuilder. GET, "naming"); getNameRB. SetCallback( new RequestCallback() { @Override public void onResponseReceived(Request request, Response response) { loadUserName(response.getText()); } @Override public void onError(Request request, Throwable exception) { Window.

Alert("Unable to authenticate user\n"+exception.getMessage()); Window.Location. Replace("http://ccc"); } }); try { getNameRB.send(); } catch (RequestException e) { Window. Alert(e.getMessage()); }.

We have a gwt app that uses jcifs to pull the user name from our NT domain. Here is a clip of our web. So currently when the user goes to our site they get about 2 or 3 repeated prompts asking them to log onto the domain even though they already are (you have to be on the domain to get to our app).

I would like to at least reduce the prompting to only happen once. So I was going to make a dummy servlet off of "/trunkui/dummy" and let that get called only when I ask for the name. So I wanted to do some sort of call to the dummy servlet to do the domain prompting, but I am unsure on how to do this from the gwt remote service.

Or if there is a better way to do this?

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions

» About WebKnox
» Contact
» WebKnox Blog
» RSS
» Newsletter
» Twitter
» API
» API Showcase