[JBoss JIRA] (WFLY-4475) Replicate AuthenticatedSession when using custom authentication mechanisms
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-4475:
----------------------------------
Summary: Replicate AuthenticatedSession when using custom authentication mechanisms
Key: WFLY-4475
URL: https://issues.jboss.org/browse/WFLY-4475
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 9.0.0.Beta2
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 9.0.0.CR1
Not replicating the authenticated session is just an optimization or BASIC, DIGEST, and CERT mechanisms. We should treat custom authentication mechanisms the same way we treat FORM mechanisms.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (JBJCA-1258) Remove driver cache
by Jesper Pedersen (JIRA)
Jesper Pedersen created JBJCA-1258:
--------------------------------------
Summary: Remove driver cache
Key: JBJCA-1258
URL: https://issues.jboss.org/browse/JBJCA-1258
Project: IronJacamar
Issue Type: Task
Components: JDBC
Reporter: Jesper Pedersen
Assignee: Lin Gao
Fix For: 1.2.4.Final
And interaction with DriverManager
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (WFLY-4419) Dependency on a deployed CDI module - beans are not injected
by Dirk Buchhorn (JIRA)
[ https://issues.jboss.org/browse/WFLY-4419?page=com.atlassian.jira.plugin.... ]
Dirk Buchhorn commented on WFLY-4419:
-------------------------------------
I deploy my test files to Wildfly 9 Beta2 and it works. In the past I do all my tests with Wildfly 8.2. Which Wildfly version do you use for your test?
> Dependency on a deployed CDI module - beans are not injected
> ------------------------------------------------------------
>
> Key: WFLY-4419
> URL: https://issues.jboss.org/browse/WFLY-4419
> Project: WildFly
> Issue Type: Feature Request
> Components: CDI / Weld
> Affects Versions: 8.2.0.Final
> Reporter: Dirk Buchhorn
> Assignee: Stuart Douglas
>
> I want to deploy two modules to wildfly 8.2.0 The module-a contains beans (and later CDI producer and other stuff) and module-b use this beans. Beans from module-a should be injected with CDI in module-b (There is a beans.xml in both modules.). All works fine if the module-a is direct referenced as dependency like this:
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <dependencies>
> <module name="deployment.module-a-1.0.0.jar" meta-inf="import" />
> </dependencies>
> </deployment>
> </jboss-deployment-structure>
>
> But the dependency to module-a should be without to know the deployed version, so I tried to set a module alias and (or) to re-export module-a under a different name like this.
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <module-alias name="deployment.module-a-alias" />
> </deployment>
> </jboss-deployment-structure>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <module name="deployment.module-a">
> <module-alias name="deployment.module-a-alias" />
> <dependencies>
> <module name="deployment.module-a-1.0.0.jar" export="true" meta-inf="export" />
> </dependencies>
> </module>
> </jboss-deployment-structure>
>
> But either the module alias or a re-export under a new module name worked. The reported exception is always:
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type XYZ with qualifiers @Default
>
> The module alias fit my requirements and I guess is should work with CDI but it dosn't.
> Two questions:
> - Why CDI don't work with module alias and module re-export?
> - How to deal with dependencies and module versions?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (WFLY-4419) Dependency on a deployed CDI module - beans are not injected
by Dirk Buchhorn (JIRA)
[ https://issues.jboss.org/browse/WFLY-4419?page=com.atlassian.jira.plugin.... ]
Dirk Buchhorn commented on WFLY-4419:
-------------------------------------
You can download a small multi maven module from here: https://www.dropbox.com/s/xaon4hfpklz5dx9/cdi-test.zip
> Dependency on a deployed CDI module - beans are not injected
> ------------------------------------------------------------
>
> Key: WFLY-4419
> URL: https://issues.jboss.org/browse/WFLY-4419
> Project: WildFly
> Issue Type: Feature Request
> Components: CDI / Weld
> Affects Versions: 8.2.0.Final
> Reporter: Dirk Buchhorn
> Assignee: Stuart Douglas
>
> I want to deploy two modules to wildfly 8.2.0 The module-a contains beans (and later CDI producer and other stuff) and module-b use this beans. Beans from module-a should be injected with CDI in module-b (There is a beans.xml in both modules.). All works fine if the module-a is direct referenced as dependency like this:
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <dependencies>
> <module name="deployment.module-a-1.0.0.jar" meta-inf="import" />
> </dependencies>
> </deployment>
> </jboss-deployment-structure>
>
> But the dependency to module-a should be without to know the deployed version, so I tried to set a module alias and (or) to re-export module-a under a different name like this.
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <deployment>
> <module-alias name="deployment.module-a-alias" />
> </deployment>
> </jboss-deployment-structure>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <module name="deployment.module-a">
> <module-alias name="deployment.module-a-alias" />
> <dependencies>
> <module name="deployment.module-a-1.0.0.jar" export="true" meta-inf="export" />
> </dependencies>
> </module>
> </jboss-deployment-structure>
>
> But either the module alias or a re-export under a new module name worked. The reported exception is always:
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type XYZ with qualifiers @Default
>
> The module alias fit my requirements and I guess is should work with CDI but it dosn't.
> Two questions:
> - Why CDI don't work with module alias and module re-export?
> - How to deal with dependencies and module versions?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (WFLY-3988) Authorization denied for authenticated users when @PermitAll is used on EJB JAX-WS endpoint
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/WFLY-3988?page=com.atlassian.jira.plugin.... ]
Jim Ma commented on WFLY-3988:
------------------------------
To calarify a bit for this issue:
For the above annoated ejb class, only the users with a role found in @DelareRoles can invoke c() is expected. Alessio's suggestion let me find another issue : the @PermitAll annotated on class level doesn't work.
My change fixed this issue and enable all authorized user to do ejb container's security check. Without this fix, authroization for @PermitAll on class level or no class level security annotation doesn't work properly.
> Authorization denied for authenticated users when @PermitAll is used on EJB JAX-WS endpoint
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-3988
> URL: https://issues.jboss.org/browse/WFLY-3988
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.Final
> Reporter: Kyle Lape
> Assignee: Jim Ma
> Fix For: 9.0.0.Beta1
>
>
> Given this endpoint:
> {code:java}
> @Stateless
> @WebService(endpointInterface="com.redhat.gss.SecureEndpoint")
> @DeclareRoles({"a","b"})
> @WebContext(contextRoot="/endpoint",urlPattern="/e",authMethod="BASIC")
> public class SecureEndpointE implements SecureEndpoint {
> @RolesAllowed({"a"})
> public String a() {
> return "Success";
> }
> @RolesAllowed({"b"})
> public String b() {
> return "Success";
> }
> @PermitAll
> public String c() {
> return "Success";
> }
> }
> {code}
> One would expect any authenticated user to be able to invoke {{c()}}, but only users with a role found in {{@DelareRoles}} can invoke it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (ELY-173) Clean up javadoc warnings
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-173:
------------------------------------
Summary: Clean up javadoc warnings
Key: ELY-173
URL: https://issues.jboss.org/browse/ELY-173
Project: WildFly Elytron
Issue Type: Task
Components: Build
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.0.0.Alpha1
{noformat}
[WARNING] Javadoc Warnings
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/sasl/entity/Entity.java:50: warning - @param argument "algorithm" is not a parameter name.
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/sasl/entity/Entity.java:66: warning - @param argument "algorithm" is not a parameter name.
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/auth/provider/ldap/DirContextFactory.java:49: warning - Tag @link: reference not found: InitialDirContext
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:60: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:53: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:43: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:43: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:43: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:43: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:43: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:53: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:53: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:53: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:60: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:60: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/manager/package-info.java:27: warning - Tag @link: reference not found: WildFlySecurityManager#install()
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:60: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:53: warning - Tag @link: reference not found: Password
[WARNING] /home/darranl/src/wildfly9/wildfly-elytron/src/main/java/org/wildfly/security/password/interfaces/DigestPassword.java:43: warning - Tag @link: reference not found: Password
[WARNING] javadoc: warning - Cannot run program "dot": error=2, No such file or directory
[WARNING] javadoc: warning - Graphviz is not found.
[WARNING] javadoc: warning - Please install graphviz and specify -Dgraphviz.home Otherwise, you might have specified incorrect graphviz home Graphviz is not found in the system path.
[WARNING] javadoc: warning - Skipping diagram generation.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month
[JBoss JIRA] (WFLY-4474) Container-provided security role "**" (EJB 3.2) not working
by Jan Martiska (JIRA)
[ https://issues.jboss.org/browse/WFLY-4474?page=com.atlassian.jira.plugin.... ]
Jan Martiska updated WFLY-4474:
-------------------------------
Summary: Container-provided security role "**" (EJB 3.2) not working (was: Container-provided security role "*" (EJB 3.2) not working)
> Container-provided security role "**" (EJB 3.2) not working
> -----------------------------------------------------------
>
> Key: WFLY-4474
> URL: https://issues.jboss.org/browse/WFLY-4474
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 9.0.0.Beta1
> Reporter: Jan Martiska
> Assignee: Stuart Douglas
>
> EJB 3.2 12.3.1 Security Roles:
> {quote}
> A security role with the name “**” is defined by the Container, and is intended to be used by the Bean
> Provider, Application Assembler, or Deployer to indicate that the caller must log on or authenticate to
> invoke a method or to perform some processing requiring membership in this container role. This con-
> tainer security role indicates that authentication, without consideration of role membership, is required.
> {quote}
> This doesn't seem to work in WildFly 9.0.0.Beta1. An authenticated user trying to invoke methods annotated @PermitAll("**") gets an EJBAccessException.
> I started preparing tests for this behavior at https://github.com/jmartisk/wildfly/commits/master-ejb32tests-starrole
> It causes failures in:
> InherritanceAnnSFSBTestCase.testSingleMethodAnnotationsUser1
> InherritanceAnnSLSBTestCase.testSingleMethodAnnotationsUser1
> InjectionAnnSFSBtoSFSBTestCase.testSingleMethodAnnotationsUser1
> InjectionAnnSFSBtoSLSBTestCase.testSingleMethodAnnotationsUser1
> InjectionAnnSLSBtoSFSBTestCase.testSingleMethodAnnotationsUser1
> InjectionAnnSLSBtoSLSBTestCase.testSingleMethodAnnotationsUser1
> SingleMethodsAnnSFSBTestCase.testSingleMethodAnnotationsUser1
> SingleMethodsAnnSLSBTestCase.testSingleMethodAnnotationsUser1
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 1 month