February 2019 - jboss-jira - Jboss List Archives

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

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1626?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1626: --------------------------------------- Unassigned for now - ELY-1464 should be improving what we cache we still need to revisit how programatic auth fits into SSO but I have some other areas I would like to revisit first such as identity propagation. > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso > --------------------------------------------------------------------------------- > > Key: ELY-1626 > URL: https://issues.jboss.org/browse/ELY-1626 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ilia Vassilev > Priority: Major > > 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.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1464) Programatic authentication should be caching the SecurityIdentity not the name of the identity

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1464?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1464: ---------------------------------- Fix Version/s: 1.6.2.CR1 > Programatic authentication should be caching the SecurityIdentity not the name of the identity > ---------------------------------------------------------------------------------------------- > > Key: ELY-1464 > URL: https://issues.jboss.org/browse/ELY-1464 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.6.2.CR1, 1.8.0.CR3 > > > By only caching the name of the identity the server authentication context -> security domain -> security realm chain is called for each subsequent request when we should have been able to re-use an existing identity. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1627) Clustered SSO does not work in simple test case

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1627?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1627: ------------------------------------- Assignee: (was: Darran Lofthouse) > Clustered SSO does not work in simple test case > ----------------------------------------------- > > Key: ELY-1627 > URL: https://issues.jboss.org/browse/ELY-1627 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ilia Vassilev > Priority: Major > > Clustered sso does not work in the following use case: > 1. start node1 and node2 > 2. hit webapp1 on node1 and login (FORM auth) > 3. stop node1 > 4. start node1 > 5. hit webapp1 on node1 ... user is asked to login again (clustered sso failed) > I have noticed that if I hit another web application (webapp2 on node1) between steps 2 and 3, then clustered sso works fine. > I use this test case to verify that customers cluster environment is working correctly and to remove load balancer issues (sticky sessions, etc) from the equation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3624) In a scenario it should be possible to create & edit only one item at a time in a collection

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3624?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3624: --------------------------------- Priority: Critical (was: Major) > In a scenario it should be possible to create & edit only one item at a time in a collection > -------------------------------------------------------------------------------------------- > > Key: DROOLS-3624 > URL: https://issues.jboss.org/browse/DROOLS-3624 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Anna Baker > Priority: Critical > Labels: ScenarioSimulation > Attachments: screencast-08-02-19-5.webm > > > If you click multiple times on "Add item" button in the collection popup, it should open only one new item form -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3639) Elytron error message less comprehensive in jdk9 compared to jdk8

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFCORE-3639?page=com.atlassian.jira.plugi... ] Martin Choma closed WFCORE-3639. -------------------------------- Resolution: Cannot Reproduce > Elytron error message less comprehensive in jdk9 compared to jdk8 > ----------------------------------------------------------------- > > Key: WFCORE-3639 > URL: https://issues.jboss.org/browse/WFCORE-3639 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Beta1 > Reporter: Martin Choma > Assignee: Jean-Francois Denise > Priority: Major > > I like jdk8 error message where there is obvious GS2-KRB5 has been attempted but failed for some reason, PLAIN has been attempted, but failed for some reason. > {code:title=jdk8} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Authentication failed: all available authentication mechanisms failed: > GS2-KRB5: javax.security.sasl.SaslException: GS2-KRB5: Server rejected authentication > PLAIN: javax.security.sasl.SaslException: ELY05053: Callback handler failed for unknown reason [Caused by java.io.IOException: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode.] > {code} > Whereas in jdk9 error message hides the fact GS2-KRB5 was attempted and just prints error for PLAIN mechanism, but does not mention explicitely it is PLAIN mechanism > {code:title=jdk9} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Cannot get password: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode. > {code} > This is general question, but I have hit this with this specific use case: > 1. server is configured to use GS2-KRB5 and PLAIN > 2. server is configured with TLS > 3. client is configured to use GS2-KRB5 > 4. expectation is authentication should be not successful because channel binding GS2-KRB5-PLUS should be used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3639) Elytron error message less comprehensive in jdk9 compared to jdk8

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFCORE-3639?page=com.atlassian.jira.plugi... ] Martin Choma commented on WFCORE-3639: -------------------------------------- Trying again with jdk 11 I see same detailed error message as with jdk 8. Closing > Elytron error message less comprehensive in jdk9 compared to jdk8 > ----------------------------------------------------------------- > > Key: WFCORE-3639 > URL: https://issues.jboss.org/browse/WFCORE-3639 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Beta1 > Reporter: Martin Choma > Assignee: Jean-Francois Denise > Priority: Major > > I like jdk8 error message where there is obvious GS2-KRB5 has been attempted but failed for some reason, PLAIN has been attempted, but failed for some reason. > {code:title=jdk8} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Authentication failed: all available authentication mechanisms failed: > GS2-KRB5: javax.security.sasl.SaslException: GS2-KRB5: Server rejected authentication > PLAIN: javax.security.sasl.SaslException: ELY05053: Callback handler failed for unknown reason [Caused by java.io.IOException: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode.] > {code} > Whereas in jdk9 error message hides the fact GS2-KRB5 was attempted and just prints error for PLAIN mechanism, but does not mention explicitely it is PLAIN mechanism > {code:title=jdk9} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Cannot get password: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode. > {code} > This is general question, but I have hit this with this specific use case: > 1. server is configured to use GS2-KRB5 and PLAIN > 2. server is configured with TLS > 3. client is configured to use GS2-KRB5 > 4. expectation is authentication should be not successful because channel binding GS2-KRB5-PLUS should be used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3591) [DMN Designer] Data Types - Type dropdown is navigable by keyboard

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3591?page=com.atlassian.jira.plugi... ] Guilherme Carreiro reassigned DROOLS-3591: ------------------------------------------ Assignee: Daniel José dos Santos (was: Guilherme Carreiro) > [DMN Designer] Data Types - Type dropdown is navigable by keyboard > ------------------------------------------------------------------ > > Key: DROOLS-3591 > URL: https://issues.jboss.org/browse/DROOLS-3591 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: 2019-01-31 15.02.26.gif > > > The following navigation between types must work in all supported browsers: > !2019-01-31 15.02.26.gif|thumbnail! > [~tirelli] reported that in some scenarios this navigation doesn't work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-289) Create Istio Helm Installation job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-289?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-289: ------------------------------------------ Parent: SWSQE-534 Issue Type: Sub-task (was: Task) > Create Istio Helm Installation job > ---------------------------------- > > Key: SWSQE-289 > URL: https://issues.jboss.org/browse/SWSQE-289 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > According to https://istio.io/docs/setup/kubernetes/helm-install/ > New job to install via helm, new jenkins slave with helm installed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3582) [DMN Designer] Data Type operation tooltips remain shown

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3582?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-3582: -------------------------------------------- Closing the https://issues.jboss.org/browse/DROOLS-3589 were solved by these PRs: https://github.com/kiegroup/kie-wb-common/pull/2466; https://github.com/kiegroup/appformer/pull/630. > [DMN Designer] Data Type operation tooltips remain shown > -------------------------------------------------------- > > Key: DROOLS-3582 > URL: https://issues.jboss.org/browse/DROOLS-3582 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.17.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2019-01-30 11-25-35.png, tooltip.webm > > > Sometimes it happens tooltip of data types operation remains shown. See steps to reproduce how to achieve this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-534) [RS] Operators

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-534?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-534: ------------------------------------------ Sprint: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18 (was: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18) > [RS] Operators > -------------- > > Key: SWSQE-534 > URL: https://issues.jboss.org/browse/SWSQE-534 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > Create an operator for installing Test Mesh -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 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 February 2019