December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14157) Internal Error accessing EJB Runtime option at Management Console

by Rodolfo Spike (Jira)

Rodolfo Spike created WFLY-14157: ------------------------------------ Summary: Internal Error accessing EJB Runtime option at Management Console Key: WFLY-14157 URL: https://issues.redhat.com/browse/WFLY-14157 Project: WildFly Issue Type: Bug Components: Management Affects Versions: 21.0.1.Final Reporter: Rodolfo Spike Assignee: Jeff Mesnil Hi, It seems that EJB Runtime monitor at Management Console is broken. I cannot monitor EJBs deployed at server because an error happens when the option is selected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 12 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2051) No acceptedIssuers is sent when CRLs are configured

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2051?page=com.atlassian.jira.plugin.... ] Farah Juma reassigned ELY-2051: ------------------------------- Assignee: (was: Farah Juma) > No acceptedIssuers is sent when CRLs are configured > --------------------------------------------------- > > Key: ELY-2051 > URL: https://issues.redhat.com/browse/ELY-2051 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.12.1.Final > Reporter: David MAFFRAND > Priority: Major > > When CRLs are configured there're no client certificate CA names sent for a tls 2 way connexion. > Method setAcceptedIssuers of X509RevocationTrustManager builder is never called, so acceptedIssuers is always empty. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 12 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2051) No acceptedIssuers is sent when CRLs are configured

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2051?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-2051: ---------------------------- Security: (was: Security Issue) > No acceptedIssuers is sent when CRLs are configured > --------------------------------------------------- > > Key: ELY-2051 > URL: https://issues.redhat.com/browse/ELY-2051 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.12.1.Final > Reporter: David MAFFRAND > Assignee: Farah Juma > Priority: Major > > When CRLs are configured there're no client certificate CA names sent for a tls 2 way connexion. > Method setAcceptedIssuers of X509RevocationTrustManager builder is never called, so acceptedIssuers is always empty. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 12 months

1
0
0 / 0

[Red Hat JIRA] (ELY-1626) Programmatic web authentication (HttpServletRequest.login()) does not trigger sso

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/ELY-1626?page=com.atlassian.jira.plugin.... ] Ilia Vassilev updated ELY-1626: ------------------------------- Attachment: login-test_eclipse.zip > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso > --------------------------------------------------------------------------------- > > Key: ELY-1626 > URL: https://issues.redhat.com/browse/ELY-1626 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ilia Vassilev > Priority: Major > Attachments: login-test.war.zip, login-test_eclipse.zip, standalone-full-ha.xml > > > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso (JSESSIONIDSSO does not get created) when using elytron/undertow. > This worked fine in EAP 6 (eap 5 too but it was a bit different as > HttpServletRequest.login() wasn't available at that time). -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 12 months

1
0
0 / 0

[Red Hat JIRA] (ELY-1626) Programmatic web authentication (HttpServletRequest.login()) does not trigger sso

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/ELY-1626?page=com.atlassian.jira.plugin.... ] Ilia Vassilev updated ELY-1626: ------------------------------- Attachment: standalone-full-ha.xml > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso > --------------------------------------------------------------------------------- > > Key: ELY-1626 > URL: https://issues.redhat.com/browse/ELY-1626 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ilia Vassilev > Priority: Major > Attachments: standalone-full-ha.xml > > > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso (JSESSIONIDSSO does not get created) when using elytron/undertow. > This worked fine in EAP 6 (eap 5 too but it was a bit different as > HttpServletRequest.login() wasn't available at that time). -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 12 months

1
0
0 / 0

[Red Hat JIRA] (ELY-1626) Programmatic web authentication (HttpServletRequest.login()) does not trigger sso

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/ELY-1626?page=com.atlassian.jira.plugin.... ] Ilia Vassilev updated ELY-1626: ------------------------------- Attachment: login-test.war.zip > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso > --------------------------------------------------------------------------------- > > Key: ELY-1626 > URL: https://issues.redhat.com/browse/ELY-1626 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ilia Vassilev > Priority: Major > Attachments: login-test.war.zip, standalone-full-ha.xml > > > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso (JSESSIONIDSSO does not get created) when using elytron/undertow. > This worked fine in EAP 6 (eap 5 too but it was a bit different as > HttpServletRequest.login() wasn't available at that time). -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 12 months

1
0
0 / 0

[Red Hat JIRA] (ELY-1626) Programmatic web authentication (HttpServletRequest.login()) does not trigger sso

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/ELY-1626?page=com.atlassian.jira.plugin.... ] Ilia Vassilev updated ELY-1626: ------------------------------- Steps to Reproduce: Start JBoss EAP with the attached configuration file standalone-full-ha.xml and deploy login-test.war. Open browser with Development console. Access http://localhost:8080/login-test/restricted Login with web form - successfully creates JSESSIONIDSSO Click on "Submit" button under "Click to programmatically login with request.login()" to trigger programmatic login - no JSESSIONIDSSO is created *Programmatic login does not create JSESSIONIDSSO:* {code} HTTP/1.1 302 Found Connection: keep-alive Location: http://localhost:8080/login-test/restricted Content-Length: 0 Date: Wed, 02 Dec 2020 16:29:23 GMT {code} *While posting to j_security_check successfully creates JSESSIONIDSSO:* {code} HTTP/1.1 302 Found Expires: 0 Connection: keep-alive Cache-Control: no-cache, no-store, must-revalidate Set-Cookie: JSESSIONIDSSO=SEJgRMi0tnzH5DM2a2ksKSgdlFaJAbW6o5VdRYle; path=/; domain=localhost Pragma: no-cache Location: http://localhost:8080/login-test/restricted Content-Length: 0 Date: Wed, 02 Dec 2020 16:25:10 GMT {code} > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso > --------------------------------------------------------------------------------- > > Key: ELY-1626 > URL: https://issues.redhat.com/browse/ELY-1626 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ilia Vassilev > Priority: Major > Attachments: standalone-full-ha.xml > > > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso (JSESSIONIDSSO does not get created) when using elytron/undertow. > This worked fine in EAP 6 (eap 5 too but it was a bit different as > HttpServletRequest.login() wasn't available at that time). -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 12 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5844) [Test Scenario] - Errors when executing models using imported inputs and/or decisions nodes

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5844?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5844: ------------------------------- Sprint: 2020 Week 46-48 (from Nov 9) (was: 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30)) > [Test Scenario] - Errors when executing models using imported inputs and/or decisions nodes > ------------------------------------------------------------------------------------------- > > Key: DROOLS-5844 > URL: https://issues.redhat.com/browse/DROOLS-5844 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulationTeam > Fix For: 7.47.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 12 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2020