July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5498) Avoid using import star in executable model classes and always use FQN

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5498?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5498: --------------------------------- Tester: Daniel Rosa Story Points: 3 > Avoid using import star in executable model classes and always use FQN > ---------------------------------------------------------------------- > > Key: DROOLS-5498 > URL: https://issues.redhat.com/browse/DROOLS-5498 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > to avoid problem such as > > ```[ERROR] /home/lmolteni/git/reproducer20200430/target/generated-sources/drools-model-compiler/main/java/org/kie/dmn/validation/DMNv1_1/Rules86f277caf99949898df882cceeb356edRuleMethods0.java:[42,260] reference to Binding is ambiguous > [ERROR] both interface org.kie.dmn.model.api.Binding in org.kie.dmn.model.api and interface org.drools.model.Binding in org.drools.model match -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5498) Avoid using import star in executable model classes and always use FQN

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5498: ------------------------------------ Summary: Avoid using import star in executable model classes and always use FQN Key: DROOLS-5498 URL: https://issues.redhat.com/browse/DROOLS-5498 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Mario Fusco to avoid problem such as ```[ERROR] /home/lmolteni/git/reproducer20200430/target/generated-sources/drools-model-compiler/main/java/org/kie/dmn/validation/DMNv1_1/Rules86f277caf99949898df882cceeb356edRuleMethods0.java:[42,260] reference to Binding is ambiguous [ERROR] both interface org.kie.dmn.model.api.Binding in org.kie.dmn.model.api and interface org.drools.model.Binding in org.drools.model match -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5498) Avoid using import star in executable model classes and always use FQN

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5498?page=com.atlassian.jira.plug... ] Luca Molteni reassigned DROOLS-5498: ------------------------------------ Assignee: Luca Molteni (was: Mario Fusco) > Avoid using import star in executable model classes and always use FQN > ---------------------------------------------------------------------- > > Key: DROOLS-5498 > URL: https://issues.redhat.com/browse/DROOLS-5498 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > to avoid problem such as > > ```[ERROR] /home/lmolteni/git/reproducer20200430/target/generated-sources/drools-model-compiler/main/java/org/kie/dmn/validation/DMNv1_1/Rules86f277caf99949898df882cceeb356edRuleMethods0.java:[42,260] reference to Binding is ambiguous > [ERROR] both interface org.kie.dmn.model.api.Binding in org.kie.dmn.model.api and interface org.drools.model.Binding in org.drools.model match -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13619) Elytron: org.wildfly.security.auth.server.SecurityIdentity not Serializable

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13619?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFLY-13619: --------------------------------------- Assignee: (was: Darran Lofthouse) > Elytron: org.wildfly.security.auth.server.SecurityIdentity not Serializable > --------------------------------------------------------------------------- > > Key: WFLY-13619 > URL: https://issues.redhat.com/browse/WFLY-13619 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 20.0.0.Final > Reporter: Andrej Kolontai > Priority: Minor > > Since the old security subsystem has been deprecated for a while I decided to move my applications to elytron which worked just fine up to the point where I tried to migrate an application that is: > * distributed > * uses Jaspic in form of a JSR375 HttpAuthenticationMechanism which has@AutoApplySession > In the logs I see stacktraces like this: > > {noformat} > 09:37:22,045 WARN [org.infinispan.PERSISTENCE] (default task-1) ISPN000559: Cannot marshall 'class org.infinispan.marshall.protostream.impl.MarshallableUserObject': java.io.NotSerializableException: org.wildfly.security.auth.server.SecurityIdentity > at org.jboss.marshalling.river@2.0.9.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:272)}} > at org.jboss.marshalling.river@2.0.9.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1141)}} > at org.jboss.marshalling.river@2.0.9.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1099)}} > at org.jboss.marshalling.river@2.0.9.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:266)}} > at org.jboss.marshalling@2.0.9.Final//org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58)}} > at org.jboss.marshalling@2.0.9.Final//org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111)}} > ..... > Caused by: an exception which occurred: > in field org.wildfly.elytron.web.undertow.server.servlet.ServletSecurityContextImpl$IdentityContainer.securityIdentity > in object org.wildfly.elytron.web.undertow.server.servlet.ServletSecurityContextImpl$IdentityContainer@7bf2af9a > in object org.wildfly.elytron.web.undertow.server.servlet.ServletSecurityContextImpl$IdentityContainer@7bf2af9a > in object java.util.concurrent.ConcurrentHashMap@d02a9ca2 > in object org.wildfly.clustering.marshalling.jboss.SimpleMarshalledValue@d02a9ca2 > {noformat} > > > Looks to me like it's trying to serialize the session to replicate it to the other nodes in the cluster and fails because the user identity, which is part of the session because of AutoApplySession, is not serializable. I have checked the source and it is really not serializable. > > I had no problems with the old security subsystem (i.e. jaspitest). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4981) Add DeploymentUnit Phases for Undertow to resolve the security domain early.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4981?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4981: ------------------------------------- Fix Version/s: 13.0.0.Beta2 > Add DeploymentUnit Phases for Undertow to resolve the security domain early. > ---------------------------------------------------------------------------- > > Key: WFCORE-4981 > URL: https://issues.redhat.com/browse/WFCORE-4981 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5020) Although elytron has module for JACC factory it is not used for JACC

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-5020?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-5020: ------------------------------------- Fix Version/s: 13.0.0.Beta2 > Although elytron has module for JACC factory it is not used for JACC > -------------------------------------------------------------------- > > Key: WFCORE-5020 > URL: https://issues.redhat.com/browse/WFCORE-5020 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 12.0.1.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta2 > > > A module can be specified and this is used to load the specified provider class and instantiate it, however this is separate to the one instantiated by PolicyConfigurationFactory. > Elytron does set a system property to ensure the configured class name is used but does not actually ensure the module is used for class loading. > At the same time it should be ensuring there is only a single instance of the class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4962) Add a SecurityMetaData for all deployments

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4962?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4962: ------------------------------------- Fix Version/s: 13.0.0.Beta2 (was: 12.0.4.Final) > Add a SecurityMetaData for all deployments > ------------------------------------------ > > Key: WFCORE-4962 > URL: https://issues.redhat.com/browse/WFCORE-4962 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta2 > > > For all deployments we should associate a new class SecurityMetaData with the deployment, initially the purpose of this will be to hold the ServiceName of any Elytron SecurityDomain if one is being used. > At a later point additional security policy information can be added as we move away from the ApplicationSecurityDomain resources. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4963) During Phase.CONFIGURE_MODULE populate SecurityMetaData with the name of any Virtual SecurityDomain

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4963?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4963: ------------------------------------- Fix Version/s: 13.0.0.Beta2 (was: 12.0.4.Final) > During Phase.CONFIGURE_MODULE populate SecurityMetaData with the name of any Virtual SecurityDomain > --------------------------------------------------------------------------------------------------- > > Key: WFCORE-4963 > URL: https://issues.redhat.com/browse/WFCORE-4963 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13220) A DeploymentException must be thrown if configured to use a PrivateKey

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13220?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFLY-13220: --------------------------------------- Assignee: (was: Darran Lofthouse) > A DeploymentException must be thrown if configured to use a PrivateKey > ---------------------------------------------------------------------- > > Key: WFLY-13220 > URL: https://issues.redhat.com/browse/WFLY-13220 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Affects Versions: 19.0.0.Beta3 > Reporter: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Beta1 > > > From section 9.2.0 of the Eclipse MicroProfile JWT specification, implementations are required to throw a DeploymentException when given a PrivateKey in any format. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12977) Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-12977?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFLY-12977: --------------------------------------- Assignee: (was: Darran Lofthouse) > Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID > ---------------------------------------------------------------------- > > Key: WFLY-12977 > URL: https://issues.redhat.com/browse/WFLY-12977 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Priority: Major > > Warning which are propagated to log from io.smallrye.jwt.auth package don't have assigned logging ID. > Example: > {code} > 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020