This content has been marked as final. Show 3 replies
I think the second pop-up is coming because of http:401 code in the header. On receiving a 401, the browsers default behavior is the basic auth pop-up.
Have you tried to check the headers? Possible way forward here would be check whether this is only observed with SSL enabled and if that is the case, try to enable ssl level debugging on the server and check whether the certificate and keystores are configured as per the requirement. But if this is irrespective of SSL, then may be we should check authentication on WLS end.
First, thanks for looking at my question.
Second, what utilities do I need in order to view the incoming messages (to the IE browser) from our Weblogic 12.c server?
Third, the message exchange appears to be part of the "standard"? negotiation of an SSL connection (with 1-way certificate authentication).
What causes Weblogic to place that code into its message header?
What can be done to prevent the Weblogic server from placing the 401 code into its message?
We have gone through the process of obtaining a signed certificate and importing it and the trust certs into the proper key stores. Would an error or omission in any of these steps cause this issue?
can you paste your web.xml here? i am interested in seeing your auth method.
you can enable debugHttp to see the request headers on WLS.
you can use fiddler to capture http headers... can u also paste your config.xml?