[
https://issues.jboss.org/browse/AS7-1054?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse commented on AS7-1054:
---------------------------------------
This is just a side effect of connections not always being kept alive so the security
being re-negotiated.
The relevent callback handlers already handle this without prompting the user for the
credentials each time so this is not an issue.
The CallbackHandler is called multiple times on the client side with
Remoting / Managent Interface
--------------------------------------------------------------------------------------------------
Key: AS7-1054
URL:
https://issues.jboss.org/browse/AS7-1054
Project: Application Server 7
Issue Type: Bug
Components: Remoting, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
This may be a side effect of the current problems where Remoting is looped to establish
the connection but it means that we need to cache the users username and password from the
first attempt so we don't keep prompting them - the problem then is we do not know if
the subsequent call is because their values were invalid or just because of the retries.
--
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