[
https://issues.jboss.org/browse/AS7-3729?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse commented on AS7-3729:
---------------------------------------
The challenge mechanism is implemented within the SASL mechanisms we use for the native
interface so there shouldn't be anything on the HTTP interface that triggers that but
it does sound weird that you are seeing the challenge created.
Admin console login fails on latest Chrome
------------------------------------------
Key: AS7-3729
URL:
https://issues.jboss.org/browse/AS7-3729
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b, 7.1.0.Final
Environment: Windows 7 Enterprise (SP1), Chrome 19.0.1036.7 dev-m
Reporter: Nicklas Karlsson
Assignee: Darran Lofthouse
Fix For: 7.1.1.Final
The application hangs at the GWT "Loading..." but never gives the password
prompt dialog. Login OK on IE9. Issues remains even if caches/passwords as cleared. From
the log:
{code}
Refused to set unsafe header "Connection"
Failed to load resource: the server responded with a status of 401 (Unauthorized)
680FEF40512BAC70B21AD8530EA085D0.cache.html:6772012-02-13 13:05:36,982 [ERROR]
Authentication required. Could not execute {
"operation" => "read-attribute",
"name" => "process-type",
"address" => []
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira