[ https://issues.jboss.org/browse/AS7-5075?page=com.atlassian.jira.plugin.s... ] Michael Gronau commented on AS7-5075: ------------------------------------- Thats a bit too difficult. But taking a look at the push(...) method in SimpleSecurityManager should help: here we run into these lines of code: // If we have a trusted identity no need for a re-auth. if (authenticated == false) { authenticated = authenticate(current, null); So, authenticate() is called with no subject as for remote calls as well, but for remote calls a current subject info is created with the user principal of the current remoting user (taken from the connection) and set in the current security context which goes into the authenticate(..) method: util.createSubjectInfo(p, credential, subject);. Here is the difference. For calls coming from an mbean for example no SubjectInfo is set for the current context before invoking authenticate(current, null). -- 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

[ https://issues.jboss.org/browse/AS7-5075?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-5075: ------------------------------------- Do you mean that you are doing a JAAS login on the mbean client, and then doing a remote JMX invocation that calls an EJB, or is the JAAS auth in the MBean method itself? -- 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

[ https://issues.jboss.org/browse/AS7-5075?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on AS7-5075: --------------------------------------- You shouldn't be calling the actual JAAS domain to authenticate at that point, instead you should call a JAAS domain that just has the ClientLoginModule - that will set the username and password so that it is used for authentication once the call reaches the EJB interceptors. -- 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

[ https://issues.jboss.org/browse/AS7-5075?page=com.atlassian.jira.plugin.s... ] jaikiran pai resolved AS7-5075. ------------------------------- Resolution: Rejected -- 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