[JBoss JIRA] (WFLY-4385) Authentication is not propagated to EJB in the login request
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-4385?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse reassigned WFLY-4385:
--------------------------------------
Assignee: (was: Darran Lofthouse)
> Authentication is not propagated to EJB in the login request
> ------------------------------------------------------------
>
> Key: WFLY-4385
> URL: https://issues.jboss.org/browse/WFLY-4385
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.2.0.Final
> Environment: MAC OSX YOSEMITE
> JAVA ORACLE 1.8
> WILDFLY 8.2.0.FINAL STANDALONE
> Reporter: Paulo Cesar Silva Reis
> Labels: authentication, ejb, http, login, roles, web
> Attachments: wildfly-4385.zip
>
>
> I'm migrating from glassfish to wildfly and noticed few weird things.
> When you perform login through web container (request.login(user, pwd)), the principal is not propagated to EJB Container, only for web container.
> To test that, this is what I did:
> . BASIC AUTH
> . EJB receives HttpServletRequest with user data and perform login
> . Print request.getUserPrincipal() => ok, logged in
> . Print EJBContext.getCallerPrincipal() => anonymous
> This happens in the same request that user logged in. In the subsequent requests (using Set-Cookie response and cookie with JSESSIONID in request), the EJB is aware of the authentication.
> Is that the right behavior? 'Cause in glassfish is different, the principal is propagated immediately to EJB.
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (SECURITY-899) Probable error code in SPNEGOLoginModule
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/SECURITY-899?page=com.atlassian.jira.plug... ]
Darran Lofthouse reassigned SECURITY-899:
-----------------------------------------
Assignee: (was: Darran Lofthouse)
> Probable error code in SPNEGOLoginModule
> ----------------------------------------
>
> Key: SECURITY-899
> URL: https://issues.jboss.org/browse/SECURITY-899
> Project: PicketBox
> Issue Type: Bug
> Components: Negotiation
> Affects Versions: Negotiation_2_2_11, Negotiation_2_3_7_Final
> Reporter: Victor Neves
> Priority: Minor
>
> Hi, first, sorry for my bad english... so, here go!
> I'm testing Jboss Negotiation Toolkit, and i configured my jboss like https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Applicatio... , but i receive this error:
> {quote}DEBUG [org.jboss.security] (http-/0.0.0.0:8080-1) PBOX000206: Login failure: javax.security.auth.login.LoginException: No NegotiationContext and no usernamePasswordDomain defined.{quote}
> Looking inter the source code, i saw:
> {quote}
> protected Object innerLogin() throws LoginException
> {
> NegotiationContext negotiationContext = NegotiationContext.getCurrentNegotiationContext();
> if (negotiationContext == null)
> {
> {color:red} if (usernamePasswordDomain == null){color}
> {
> throw new LoginException("No NegotiationContext and no usernamePasswordDomain defined.");
> }
> return usernamePasswordLogin();
> }
> else
> {
> return spnegoLogin(negotiationContext);
> }
> }{quote}
> But the documentation dont say anything about _usernamePasswordDomain_ !! And in the fisrt IF the _negotiationContext_ ALWAYS return NULL !! I dont kown if its a bug ...
> this is my configuration in JBoss EAP 6.3 :
> {quote}
> <security-domain name="kerberos" cache-type="default">
> <authentication>
> <login-module code="com.sun.security.auth.module.Krb5LoginModule" flag="required">
> <module-option name="storeKey" value="true"/>
> <module-option name="useKeyTab" value="true"/>
> <module-option name="doNotPrompt" value="true"/>
> <module-option name="debug" value="true"/>
> <module-option name="principal" value="victor(a)MY_REALM.BR"/>
> <module-option name="keyTab" value="C:\desenvolvimento\webserver\appserver.keytab"/>
> </login-module>
> </authentication>
> </security-domain>
> <security-domain name="SPNEGO" cache-type="default">
> <authentication>
> <login-module code="org.jboss.security.negotiation.spnego.SPNEGOLoginModule" flag="requisite">
> <module-option name="password-stacking" value="useFirstPass"/>
> <module-option name="serverSecurityDomain" value="kerberos"/>
> </login-module>
> <login-module code="org.jboss.security.negotiation.AdvancedLdapLoginModule" flag="required">
> <module-option name="allowEmptyPasswords" value="true"/>
> <module-option name="throwValidateError" value="true"/>
> <module-option name="searchTimeLimit" value="5000"/>
> <module-option name="baseCtxDN" value="ou=People,o=victor,dc=xxx,dc=yyy"/>
> <module-option name="baseFilter" value="(uid= 0 )"/>
> <module-option name="roleAttributeIsDN" value="true"/>
> <module-option name="roleAttributeID" value="cn"/>
> <module-option name="roleNameAttributeID" value="cn"/>
> <module-option name="java.naming.provider.url" value="ldap://xx.xxx.xx.xx:389"/>
> <module-option name="roleFilter" value="(uniqueMember=uid= 0,ou=People,o=victor,dc=xxx,dc=yyy)"/>
> <module-option name="rolesCtxDN" value="cn=SIABC,ou=Groups,o=victor,dc=xxx,dc=yyy"/>
> </login-module>
> </authentication>
> </security-domain>
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-4338) JConsole script builds wrong path
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-4338?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse reassigned WFLY-4338:
--------------------------------------
Assignee: (was: Darran Lofthouse)
> JConsole script builds wrong path
> ---------------------------------
>
> Key: WFLY-4338
> URL: https://issues.jboss.org/browse/WFLY-4338
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 8.2.0.Final
> Environment: Linux (Ubuntu 14.10) and Mac OS X Yosemite (10.10.2)
> Reporter: André Lemos
> Labels: bash, jconsole, wildfly
> Attachments: jconsole.patch
>
>
> The path built by the jconsole.sh script is incorrect, and as a result, when calling {{service:jmx:http-remoting-jmx://{insert server ip here}:9990}} is probably never recognized and the connection is never done.
> The path, under mac is:
> {{/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/jconsole -J-Djava.class.path=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/jconsole.jar:/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/tools.jar:"/Users/user/Documents/playground/wild/wildfly-8.2.0.Final"/bin/client/jboss-cli-client.jar}}
> So, there are " on the path for the jboss-cli-client.jar. which breaks things. This problem happens with both Linux and Mac.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (REMJMX-104) Xnio Options passed in environment are not passed down
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/REMJMX-104?page=com.atlassian.jira.plugin... ]
Darran Lofthouse reassigned REMJMX-104:
---------------------------------------
Assignee: (was: Darran Lofthouse)
> Xnio Options passed in environment are not passed down
> ------------------------------------------------------
>
> Key: REMJMX-104
> URL: https://issues.jboss.org/browse/REMJMX-104
> Project: Remoting JMX
> Issue Type: Bug
> Components: Connection
> Affects Versions: 1.1.3.Final
> Reporter: Brad Maxwell
>
> XNIO options are not passed down when specified in the environment, preventing the client from specifying things such as SSL_ENABLED=false
>
> {code}
> JMXServiceURL jmxUrl = new JMXServiceURL(url);
> Hashtable env = new Hashtable();
> env.put("org.xnio.Options.SSL_ENABLED","false");
> String[] credentials = new String[] { user, pass };
> env.put(JMXConnector.CREDENTIALS, credentials);
> this.jmxConnector = JMXConnectorFactory.connect(jmxUrl, env);
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months