July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3691) AuditProvider mentions "[Success]" even if username/password is invalid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3691?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3691: ----------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1054556|https://bugzilla.redhat.com/show_bug.cgi?id=1054556] from ASSIGNED to POST > AuditProvider mentions "[Success]" even if username/password is invalid > ----------------------------------------------------------------------- > > Key: WFLY-3691 > URL: https://issues.jboss.org/browse/WFLY-3691 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Josef Cacek > Assignee: Josef Cacek > > Description of problem: > AuditProvider in security-domain mentions "[Success]" as follow:- > 11:37:26,835 TRACE [org.jboss.security.audit] (HttpManagementService-threads - 3) [Success]Source=org.jboss.as.security.service.SimpleSecurityManager;Action=authentication;principal=admin; > even if a username/password is wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3691) AuditProvider mentions "[Success]" even if username/password is invalid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3691?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3691: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1054556 > AuditProvider mentions "[Success]" even if username/password is invalid > ----------------------------------------------------------------------- > > Key: WFLY-3691 > URL: https://issues.jboss.org/browse/WFLY-3691 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Josef Cacek > Assignee: Josef Cacek > > Description of problem: > AuditProvider in security-domain mentions "[Success]" as follow:- > 11:37:26,835 TRACE [org.jboss.security.audit] (HttpManagementService-threads - 3) [Success]Source=org.jboss.as.security.service.SimpleSecurityManager;Action=authentication;principal=admin; > even if a username/password is wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3691) AuditProvider mentions "[Success]" even if username/password is invalid

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-3691?page=com.atlassian.jira.plugin.... ] Josef Cacek updated WFLY-3691: ------------------------------ Affects Version/s: 8.1.0.Final > AuditProvider mentions "[Success]" even if username/password is invalid > ----------------------------------------------------------------------- > > Key: WFLY-3691 > URL: https://issues.jboss.org/browse/WFLY-3691 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.1.0.Final > Reporter: Josef Cacek > Assignee: Josef Cacek > > Description of problem: > AuditProvider in security-domain mentions "[Success]" as follow:- > 11:37:26,835 TRACE [org.jboss.security.audit] (HttpManagementService-threads - 3) [Success]Source=org.jboss.as.security.service.SimpleSecurityManager;Action=authentication;principal=admin; > even if a username/password is wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3691) AuditProvider mentions "[Success]" even if username/password is invalid

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-3691?page=com.atlassian.jira.plugin.... ] Josef Cacek updated WFLY-3691: ------------------------------ Component/s: Security > AuditProvider mentions "[Success]" even if username/password is invalid > ----------------------------------------------------------------------- > > Key: WFLY-3691 > URL: https://issues.jboss.org/browse/WFLY-3691 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Josef Cacek > Assignee: Josef Cacek > > Description of problem: > AuditProvider in security-domain mentions "[Success]" as follow:- > 11:37:26,835 TRACE [org.jboss.security.audit] (HttpManagementService-threads - 3) [Success]Source=org.jboss.as.security.service.SimpleSecurityManager;Action=authentication;principal=admin; > even if a username/password is wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3691) AuditProvider mentions "[Success]" even if username/password is invalid

by Josef Cacek (JIRA)

Josef Cacek created WFLY-3691: --------------------------------- Summary: AuditProvider mentions "[Success]" even if username/password is invalid Key: WFLY-3691 URL: https://issues.jboss.org/browse/WFLY-3691 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Josef Cacek Assignee: Jason Greene Description of problem: AuditProvider in security-domain mentions "[Success]" as follow:- 11:37:26,835 TRACE [org.jboss.security.audit] (HttpManagementService-threads - 3) [Success]Source=org.jboss.as.security.service.SimpleSecurityManager;Action=authentication;principal=admin; even if a username/password is wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3691) AuditProvider mentions "[Success]" even if username/password is invalid

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-3691?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-3691: --------------------------------- Assignee: Josef Cacek (was: Jason Greene) > AuditProvider mentions "[Success]" even if username/password is invalid > ----------------------------------------------------------------------- > > Key: WFLY-3691 > URL: https://issues.jboss.org/browse/WFLY-3691 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Josef Cacek > Assignee: Josef Cacek > > Description of problem: > AuditProvider in security-domain mentions "[Success]" as follow:- > 11:37:26,835 TRACE [org.jboss.security.audit] (HttpManagementService-threads - 3) [Success]Source=org.jboss.as.security.service.SimpleSecurityManager;Action=authentication;principal=admin; > even if a username/password is wrong. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-784) LdapExtLoginModule cannot find custom ldap socket factory

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/SECURITY-784?page=com.atlassian.jira.plug... ] Josef Cacek commented on SECURITY-784: -------------------------------------- During fixing, could you also consider following points? * custom {{INITIAL_CONTEXT_FACTORY}} loaded from another module * fix the behavior in another LDAP login modules too (both PicketBox and JBoss Negotiation) > LdapExtLoginModule cannot find custom ldap socket factory > --------------------------------------------------------- > > Key: SECURITY-784 > URL: https://issues.jboss.org/browse/SECURITY-784 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-784.patch > > > LdapExtLoginModule cannot find custom ldap socket factory. > Passing the "java.naming.ldap.factory.socket" property in as an > module-option: > <module-option name="java.naming.ldap.factory.socket" value="org.jboss.example.CustomSocketFactory"/> > results in a ClassNotFoundException: > Caused by: javax.naming.CommunicationException: 192.168.1.8:389 [Root exception is java.lang.ClassNotFoundException: org/jboss/example/CustomSocketFactory] > at com.sun.jndi.ldap.Connection.<init>(Connection.java:226) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:136) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1608) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2698) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) [rt.jar:1.7.0_45] > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.7.0_45] > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) [rt.jar:1.7.0_45] > at javax.naming.InitialContext.init(InitialContext.java:242) [rt.jar:1.7.0_45] > at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153) [rt.jar:1.7.0_45] > at org.jboss.security.auth.spi.LdapExtLoginModule.constructInitialLdapContext(LdapExtLoginModule.java:767) [picketbox-4.0.17.SP2-redhat-2.jar:4.0.17.SP2-redhat-2] > I tried making the custom socket factory into a jboss module and adding the module as a dependency to picketbox and > sun.jdk. Unfortunately, that did not work. I also added the socket > factory jar to the jre/lib/ext directory. That didn't work either. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-784) LdapExtLoginModule cannot find custom ldap socket factory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-784?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-784: -------------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1068665|https://bugzilla.redhat.com/show_bug.cgi?id=1068665] from NEW to CLOSED > LdapExtLoginModule cannot find custom ldap socket factory > --------------------------------------------------------- > > Key: SECURITY-784 > URL: https://issues.jboss.org/browse/SECURITY-784 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-784.patch > > > LdapExtLoginModule cannot find custom ldap socket factory. > Passing the "java.naming.ldap.factory.socket" property in as an > module-option: > <module-option name="java.naming.ldap.factory.socket" value="org.jboss.example.CustomSocketFactory"/> > results in a ClassNotFoundException: > Caused by: javax.naming.CommunicationException: 192.168.1.8:389 [Root exception is java.lang.ClassNotFoundException: org/jboss/example/CustomSocketFactory] > at com.sun.jndi.ldap.Connection.<init>(Connection.java:226) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:136) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1608) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2698) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154) [rt.jar:1.7.0_45] > at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84) [rt.jar:1.7.0_45] > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.7.0_45] > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) [rt.jar:1.7.0_45] > at javax.naming.InitialContext.init(InitialContext.java:242) [rt.jar:1.7.0_45] > at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153) [rt.jar:1.7.0_45] > at org.jboss.security.auth.spi.LdapExtLoginModule.constructInitialLdapContext(LdapExtLoginModule.java:767) [picketbox-4.0.17.SP2-redhat-2.jar:4.0.17.SP2-redhat-2] > I tried making the custom socket factory into a jboss module and adding the module as a dependency to picketbox and > sun.jdk. Unfortunately, that did not work. I also added the socket > factory jar to the jre/lib/ext directory. That didn't work either. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3690) split xts-enviroment's URL attribute in 4 different attribute

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3690?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3690: ----------------------------------------------- Stefano Maestri <smaestri(a)redhat.com> changed the Status of [bug 1077156|https://bugzilla.redhat.com/show_bug.cgi?id=1077156] from NEW to ASSIGNED > split xts-enviroment's URL attribute in 4 different attribute > ------------------------------------------------------------- > > Key: WFLY-3690 > URL: https://issues.jboss.org/browse/WFLY-3690 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > Currently we have the following configuration element: <xts-environment url="http://${jboss.bind.address:127.0.0.1}:8080/ws-c11/ActivationService"/> > we need to split url in 4 different attribute: > * protocol > * host > * port > * path -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3690) split xts-enviroment's URL attribute in 4 different attribute

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3690?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3690: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1077156 > split xts-enviroment's URL attribute in 4 different attribute > ------------------------------------------------------------- > > Key: WFLY-3690 > URL: https://issues.jboss.org/browse/WFLY-3690 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > Currently we have the following configuration element: <xts-environment url="http://${jboss.bind.address:127.0.0.1}:8080/ws-c11/ActivationService"/> > we need to split url in 4 different attribute: > * protocol > * host > * port > * path -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2014