June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13566) Ensure that Jandex indexes are released from JPA deployment memory after deployment completes

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-13566?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-13566: --------------------------------- Labels: downstream_dependency (was: ) > Ensure that Jandex indexes are released from JPA deployment memory after deployment completes > --------------------------------------------------------------------------------------------- > > Key: WFLY-13566 > URL: https://issues.redhat.com/browse/WFLY-13566 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.2.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > org.jboss.as.jpa.service.PersistenceUnitServiceImpl#start() needs to always call pu.setAnnotationIndex(null) to clear the deployment reference to the Jandex Indexes. > Currently without the fix, the Jandex Index will be released at application undeployment time. With the fix, the Jandex Index memory will be released after application deployment is complete. Note that the Jandex Index contains metadata for the application deployment classes and are not needed after deployment is complete. > Note that this problem shouldn't occur when persistence.xml contains: > {code} > <property name="wildfly.jpa.twophasebootstrap" value="false"/> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13586) Add a Galleon layer for JSONB

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13586: ------------------------------------------- Summary: Add a Galleon layer for JSONB Key: WFLY-13586 URL: https://issues.redhat.com/browse/WFLY-13586 Project: WildFly Issue Type: Feature Request Components: Build System Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana Create a Galleon layer to provision JsonB API and Impl modules. These modules are optionally provisioned by jaxrs, jaxrs-server and cloud-server. We can use this layer to add them on top of any other layer, or provision them even if optional dependencies are excluded. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13585) Add a Galleon layer for JSONP

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13585: ------------------------------------------- Summary: Add a Galleon layer for JSONP Key: WFLY-13585 URL: https://issues.redhat.com/browse/WFLY-13585 Project: WildFly Issue Type: Feature Request Components: Build System Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana Create a Galleon layer to provision JsonP API and Impl modules. These modules already belong to the base server, so the idea with this layer is just to ensure they are provisioned independently if they are excluded in the future from the base-server layer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3313) Websocket Auth - Container is not aware of the Principal

by Caleb Adams (Jira)

[ https://issues.redhat.com/browse/WFLY-3313?page=com.atlassian.jira.plugin... ] Caleb Adams commented on WFLY-3313: ----------------------------------- This is also occurring on WildFly 17.0.1.Final... EJBContext returns the anonymous principal and @RolesAllowed checks within the EJB container are broken. > Websocket Auth - Container is not aware of the Principal > -------------------------------------------------------- > > Key: WFLY-3313 > URL: https://issues.redhat.com/browse/WFLY-3313 > Project: WildFly > Issue Type: Bug > Components: EJB, Security, Web (Undertow), Web Sockets > Affects Versions: 8.1.0.CR1, 10.0.0.Final, 15.0.0.Final > Reporter: Markus D > Priority: Major > Attachments: websocket-different-principals-ejb-vs-socket.png, websocket-endpoint-security.war > > > The Websocket is protected by the web.xml. The session object of the callback object correctly returns the principal. > When an EJB is called the callerPrincipal is always anonymous. > @Resource > private SessionContext ctx; > Principal callerPrincipal = ctx.getCallerPrincipal(); > Running thread here: > https://community.jboss.org/thread/240617 > Shouldn't the principal be propagated to the EJB container when a websocket callback method triggered? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-966) UI Automations - Check Traces tab functionality

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-966?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan resolved SWSQE-966. ---------------------------------- Resolution: Done https://github.com/Kiali-QE/kiali-qe-python/pull/302 > UI Automations - Check Traces tab functionality > ----------------------------------------------- > > Key: SWSQE-966 > URL: https://issues.redhat.com/browse/SWSQE-966 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Traces tab of Kiali is not automated in UI Automations framework. > We need to automate: > 1. Traces menu clicking and verifying the opened page. > 2. Traces tab. Click, no errors, no login asked. > 3. Search Traces in Traces tab. Verify that it shows traces or a message that traces does not exist. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1996) SSLContext to support delegation to alternate instances based on peer information.

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1996?page=com.atlassian.jira.plugin.... ] Farah Juma moved EAP7-1502 to ELY-1996: --------------------------------------- Project: WildFly Elytron (was: JBoss EAP Planning for version 7 and above) Key: ELY-1996 (was: EAP7-1502) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: (was: Security) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.4.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > SSLContext to support delegation to alternate instances based on peer information. > ---------------------------------------------------------------------------------- > > Key: ELY-1996 > URL: https://issues.redhat.com/browse/ELY-1996 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Farah Juma > Assignee: Diana Vilkolakova > Priority: Major > Labels: Active-Development > > As an SSLEngine is created the host and port information is available at the time the engine is requested: - > https://download.java.net/java/early_access/jdk11/docs/api/java.base/java... > We could make use of this information to dynamically select alternative configurations. > This would also be a natural follow up to EAP7-1096 so the registered SSLContext could delegate to different configurations based on destination. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13571) JSF: selectOneMenu required+disabled true

by Cody Lerum (Jira)

[ https://issues.redhat.com/browse/WFLY-13571?page=com.atlassian.jira.plugi... ] Cody Lerum commented on WFLY-13571: ----------------------------------- I've run into this same issue after moving to Wildfly 20 Additionally a possibly related issue regression is when submitted a form with a {code:java} <h:selectBooleanCheckbox value=#{bean.foo} disabled="true" />{code} Results in an NPE {code:java} java.lang.NullPointerException: Cannot invoke "Object.toString()" because "submittedValue" is null java.lang.NullPointerException: Cannot invoke "Object.toString()" because "submittedValue" is null at com.sun.jsf-impl@2.3.9.SP10//com.sun.faces.renderkit.html_basic.CheckboxRenderer.getConvertedValue(CheckboxRenderer.java:95) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIInput.getConvertedValue(UIInput.java:1109) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIInput.validate(UIInput.java:991) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIInput.executeValidate(UIInput.java:1321) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIInput.processValidators(UIInput.java:733) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:921) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:921) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIForm.processValidators(UIForm.java:229) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:921) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:921) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:921) at javax.faces.api@3.0.0.SP03//javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:1310) at com.sun.jsf-impl@2.3.9.SP10//com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:53) at com.sun.jsf-impl@2.3.9.SP10//com.sun.faces.lifecycle.Phase.doPhase(Phase.java:76) at com.sun.jsf-impl@2.3.9.SP10//com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177) at javax.faces.api@3.0.0.SP03//javax.faces.webapp.FacesServlet.executeLifecyle(FacesServlet.java:707) at javax.faces.api@3.0.0.SP03//javax.faces.webapp.FacesServlet.service(FacesServlet.java:451) at io.undertow.servlet@2.1.3.Final//io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) {code} > JSF: selectOneMenu required+disabled true > ----------------------------------------- > > Key: WFLY-13571 > URL: https://issues.redhat.com/browse/WFLY-13571 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 20.0.0.Final > Reporter: erick leal > Assignee: Farah Juma > Priority: Major > Attachments: project.zip > > > Submitin selectOneMenu required=true+disabled=true result in validation error message. > Regression in WildFly 20, clicking button fires a message. > WildFly 19 it's ok. > Mojarra issue: https://github.com/eclipse-ee4j/mojarra/issues/4716 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1995) AggregateRealm is failing in authentication with token-realm

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1995?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1995: ---------------------------- Security: (was: Red Hat Internal) > AggregateRealm is failing in authentication with token-realm > ------------------------------------------------------------ > > Key: ELY-1995 > URL: https://issues.redhat.com/browse/ELY-1995 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Farah Juma > Priority: Major > > Authentication is failing when token-realm is set as an authentication-realm in aggregate-realm and ldap-realm is set as authorization realm. > It is found that {{AggregateSecurityRealm#getRealmIdentity}} is attempting to get the realm identity to be used for authentication using the JWT realm and it attempts to get the realm identity to be used for authorization using the LDAP realm. In both cases, the {{BearerTokenEvidence}} is being used to try to obtain the realm identity. The problem with this is that the {{LdapSecurityRealm}} won't be able to obtain the principal from the {{BearerTokenEvidence}} so the {{authorizationIdentity}} will just be the {{RealmIdentity.NON_EXISTENT}} identity, resulting in the "User does not exist" error. > {panel} > 2020-06-11 08:51:06,767 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='BEARER_TOKEN' host-name='localhost' protocol='http' > 2020-06-11 08:51:06,769 TRACE [org.wildfly.security] (default task-1) Evidence verification: evidence = org.wildfly.security.evidence.BearerTokenEvidence@2587e47f evidencePrincipal = null > 2020-06-11 08:51:06,782 DEBUG [org.wildfly.security] (default task-1) Token is using algorithm [RS256] > 2020-06-11 08:51:06,789 DEBUG [org.wildfly.security] (default task-1) Token is using algorithm [RS256] > 2020-06-11 08:51:06,792 TRACE [org.wildfly.security] (default task-1) BEARER_TOKEN: org.wildfly.security.http.HttpAuthenticationException: ELY05053: Callback handler failed for unknown reason > at org.wildfly.security.mechanism._private.MechanismUtil.handleCallbacks(MechanismUtil.java:161) > ... 41 more > {panel} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1995) AggregateRealm is failing in authentication with token-realm

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1995?page=com.atlassian.jira.plugin.... ] Farah Juma reassigned ELY-1995: ------------------------------- Assignee: Farah Juma > AggregateRealm is failing in authentication with token-realm > ------------------------------------------------------------ > > Key: ELY-1995 > URL: https://issues.redhat.com/browse/ELY-1995 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > Authentication is failing when token-realm is set as an authentication-realm in aggregate-realm and ldap-realm is set as authorization realm. > It is found that {{AggregateSecurityRealm#getRealmIdentity}} is attempting to get the realm identity to be used for authentication using the JWT realm and it attempts to get the realm identity to be used for authorization using the LDAP realm. In both cases, the {{BearerTokenEvidence}} is being used to try to obtain the realm identity. The problem with this is that the {{LdapSecurityRealm}} won't be able to obtain the principal from the {{BearerTokenEvidence}} so the {{authorizationIdentity}} will just be the {{RealmIdentity.NON_EXISTENT}} identity, resulting in the "User does not exist" error. > {panel} > 2020-06-11 08:51:06,767 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='BEARER_TOKEN' host-name='localhost' protocol='http' > 2020-06-11 08:51:06,769 TRACE [org.wildfly.security] (default task-1) Evidence verification: evidence = org.wildfly.security.evidence.BearerTokenEvidence@2587e47f evidencePrincipal = null > 2020-06-11 08:51:06,782 DEBUG [org.wildfly.security] (default task-1) Token is using algorithm [RS256] > 2020-06-11 08:51:06,789 DEBUG [org.wildfly.security] (default task-1) Token is using algorithm [RS256] > 2020-06-11 08:51:06,792 TRACE [org.wildfly.security] (default task-1) BEARER_TOKEN: org.wildfly.security.http.HttpAuthenticationException: ELY05053: Callback handler failed for unknown reason > at org.wildfly.security.mechanism._private.MechanismUtil.handleCallbacks(MechanismUtil.java:161) > ... 41 more > {panel} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1995) AggregateRealm is failing in authentication with token-realm

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1995?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1995: ---------------------------- > AggregateRealm is failing in authentication with token-realm > ------------------------------------------------------------ > > Key: ELY-1995 > URL: https://issues.redhat.com/browse/ELY-1995 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > Authentication is failing when token-realm is set as an authentication-realm in aggregate-realm and ldap-realm is set as authorization realm. > It is found that {{AggregateSecurityRealm#getRealmIdentity}} is attempting to get the realm identity to be used for authentication using the JWT realm and it attempts to get the realm identity to be used for authorization using the LDAP realm. In both cases, the {{BearerTokenEvidence}} is being used to try to obtain the realm identity. The problem with this is that the {{LdapSecurityRealm}} won't be able to obtain the principal from the {{BearerTokenEvidence}} so the {{authorizationIdentity}} will just be the {{RealmIdentity.NON_EXISTENT}} identity, resulting in the "User does not exist" error. > {panel} > 2020-06-11 08:51:06,767 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='BEARER_TOKEN' host-name='localhost' protocol='http' > 2020-06-11 08:51:06,769 TRACE [org.wildfly.security] (default task-1) Evidence verification: evidence = org.wildfly.security.evidence.BearerTokenEvidence@2587e47f evidencePrincipal = null > 2020-06-11 08:51:06,782 DEBUG [org.wildfly.security] (default task-1) Token is using algorithm [RS256] > 2020-06-11 08:51:06,789 DEBUG [org.wildfly.security] (default task-1) Token is using algorithm [RS256] > 2020-06-11 08:51:06,792 TRACE [org.wildfly.security] (default task-1) BEARER_TOKEN: org.wildfly.security.http.HttpAuthenticationException: ELY05053: Callback handler failed for unknown reason > at org.wildfly.security.mechanism._private.MechanismUtil.handleCallbacks(MechanismUtil.java:161) > ... 41 more > {panel} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 June 2020