April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1029) Support clients that provide an optional CallbackHandler

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1029?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1029: ---------------------------------- Fix Version/s: 1.1.0.Beta36 (was: 1.1.0.Beta35) > Support clients that provide an optional CallbackHandler > -------------------------------------------------------- > > Key: ELY-1029 > URL: https://issues.jboss.org/browse/ELY-1029 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta36 > > > Clients such as the WildFly CLI provide a CallbackHandler implementation in case it is needed and not as a sign that it must be used, i.e. the desired outcome is that if the information required can be obtained from the configuration then authentication proceeds without interaction with the end user. > Neither the CLI or the end user should be required to be fully aware of the underlying security configuration. > This is similar to web browser HTTP authentication where there is only an interaction with the user if actually required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1028) AuthenticationException should extend IOException

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1028?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1028: ---------------------------------- Fix Version/s: 1.1.0.Beta36 (was: 1.1.0.Beta35) > AuthenticationException should extend IOException > ------------------------------------------------- > > Key: ELY-1028 > URL: https://issues.jboss.org/browse/ELY-1028 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta36 > > > Remote authentications use I/O. AuthenticationException pertains solely to remote authentications. Therefore it (like SaslException and many others) should extend IOException, not GeneralSecurityException. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1063) Release WildFly Elytron 1.1.0.Beta35

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1063?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1063. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta35 > ------------------------------------ > > Key: ELY-1063 > URL: https://issues.jboss.org/browse/ELY-1063 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta35 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat SSL

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1516: ------------------------------------- Assignee: Toni Rikkola (was: Edson Tirelli) > GAV names are not coming properly when running the tomcat SSL > ------------------------------------------------------------- > > Key: DROOLS-1516 > URL: https://issues.jboss.org/browse/DROOLS-1516 > Project: Drools > Issue Type: Bug > Components: build, kie server, tools > Affects Versions: 6.5.0.Final > Environment: Windows > Reporter: Arunraj SRM > Assignee: Toni Rikkola > Priority: Critical > Labels: Drools, GAV,, Maven > Attachments: gav_issue.png > > > Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as > <undetermined>:<undetermined>:<undetermined> > instead of actual path including the guvnor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8526) Confusion in method with(AuthenticationContext other) in AuthenticationContext

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8526?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-8526: -------------------------------------- Assignee: Darran Lofthouse (was: Jan Kalina) > Confusion in method with(AuthenticationContext other) in AuthenticationContext > ------------------------------------------------------------------------------ > > Key: WFLY-8526 > URL: https://issues.jboss.org/browse/WFLY-8526 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Labels: api, authentication-context > Fix For: 11.0.0.Beta1 > > > org.wildfly.security.auth.client.AuthenticationContext includes method {{AuthenticationContext with(AuthenticationContext other)}} which creates new AuthenticationContext which includes rules and configuration and SSL context of given AuthenticationContext other. > However, in case when {{with}} method is used with index and another AuthenticationContext, then it includes only rules and configuration (SSL context is not used). There is also method {{withSsl}} which includes rules and SSL context, but no configuration. > I see three problems here: > * there is different behavior between {{with(AuthenticationContext other)}} and {{with(int idx, AuthenticationContext other)}} - first includes also SSL context > * javadoc for with(AuthenticationContext other) does not describe that SSL context from given {{AuthenticationContext other}} is also used. > * there is not able to include both configuration and SSL context into any AuthenticationContext on some position based on index > I report this as critical because it is part of public API - it should stay backward compatible once it will be released. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8526) Confusion in method with(AuthenticationContext other) in AuthenticationContext

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8526?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8526: ----------------------------------- Fix Version/s: 11.0.0.Beta1 > Confusion in method with(AuthenticationContext other) in AuthenticationContext > ------------------------------------------------------------------------------ > > Key: WFLY-8526 > URL: https://issues.jboss.org/browse/WFLY-8526 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Labels: api, authentication-context > Fix For: 11.0.0.Beta1 > > > org.wildfly.security.auth.client.AuthenticationContext includes method {{AuthenticationContext with(AuthenticationContext other)}} which creates new AuthenticationContext which includes rules and configuration and SSL context of given AuthenticationContext other. > However, in case when {{with}} method is used with index and another AuthenticationContext, then it includes only rules and configuration (SSL context is not used). There is also method {{withSsl}} which includes rules and SSL context, but no configuration. > I see three problems here: > * there is different behavior between {{with(AuthenticationContext other)}} and {{with(int idx, AuthenticationContext other)}} - first includes also SSL context > * javadoc for with(AuthenticationContext other) does not describe that SSL context from given {{AuthenticationContext other}} is also used. > * there is not able to include both configuration and SSL context into any AuthenticationContext on some position based on index > I report this as critical because it is part of public API - it should stay backward compatible once it will be released. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat SSL

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1516: ---------------------------------- Priority: Critical (was: Blocker) > GAV names are not coming properly when running the tomcat SSL > ------------------------------------------------------------- > > Key: DROOLS-1516 > URL: https://issues.jboss.org/browse/DROOLS-1516 > Project: Drools > Issue Type: Bug > Components: build, kie server, tools > Affects Versions: 6.5.0.Final > Environment: Windows > Reporter: Arunraj SRM > Assignee: Edson Tirelli > Priority: Critical > Labels: Drools, GAV,, Maven > Attachments: gav_issue.png > > > Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as > <undetermined>:<undetermined>:<undetermined> > instead of actual path including the guvnor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8526) Confusion in method with(AuthenticationContext other) in AuthenticationContext

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8526?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved JBEAP-10185 to WFLY-8526: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8526 (was: JBEAP-10185) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: (was: 7.1.0.DR13) > Confusion in method with(AuthenticationContext other) in AuthenticationContext > ------------------------------------------------------------------------------ > > Key: WFLY-8526 > URL: https://issues.jboss.org/browse/WFLY-8526 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Labels: api, authentication-context > Fix For: 11.0.0.Beta1 > > > org.wildfly.security.auth.client.AuthenticationContext includes method {{AuthenticationContext with(AuthenticationContext other)}} which creates new AuthenticationContext which includes rules and configuration and SSL context of given AuthenticationContext other. > However, in case when {{with}} method is used with index and another AuthenticationContext, then it includes only rules and configuration (SSL context is not used). There is also method {{withSsl}} which includes rules and SSL context, but no configuration. > I see three problems here: > * there is different behavior between {{with(AuthenticationContext other)}} and {{with(int idx, AuthenticationContext other)}} - first includes also SSL context > * javadoc for with(AuthenticationContext other) does not describe that SSL context from given {{AuthenticationContext other}} is also used. > * there is not able to include both configuration and SSL context into any AuthenticationContext on some position based on index > I report this as critical because it is part of public API - it should stay backward compatible once it will be released. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1367) Migrate Drools preferences to the new Preferences API

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1367?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1367: ------------------------------------- Assignee: Toni Rikkola (was: Edson Tirelli) > Migrate Drools preferences to the new Preferences API > ----------------------------------------------------- > > Key: DROOLS-1367 > URL: https://issues.jboss.org/browse/DROOLS-1367 > Project: Drools > Issue Type: Bug > Reporter: Paulo Rego > Assignee: Toni Rikkola > > Now that the new Preferences API is configured in the workbench, we should migrate all necessary jBPM preferences to use it, thus allowing the user to edit them. > Here we have [a doc|https://docs.google.com/document/d/1P3N1PH6arUjEKgIONLSJbhCDIqaY_xQNR...] enumerating some preferences. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-81) Baseline #3

by viet nguyen (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-81?page=com.atlassian.jira.plu... ] viet nguyen edited comment on HAWKULARQE-81 at 4/6/17 1:36 PM: --------------------------------------------------------------- [^promgen-analytic-12hr.png] gives a snapshot of raw metrics tallies during a 12 hour run of 230 pods. Grafana dashboard url: http://hawkular-grafana-analytics.cloud2.jonqe.lab.eng.bos.redhat.com/das... (data may be pursed automatically after 14 days) Expected raw data points per 15 minute interval: 30 Observations: - As seen in the top graph raw metrics dip below 20 - there are metrics definitions but 0 data for some pods - I suspect the dips were caused by pod restarts but that is not the case. I randomly selected 2 pods, 1 with restart and 1 without restart and graph their data counts. Next step: - store metrics id by pod name as oppose to pod UID for easier cross references with output of oc commands - reduce the number of pod to see if there are still dips - I just notice a flaw in my Python analytic tool - it fetches *all* metric definitions (including metrics of pods that are from previous test runs) Need to only get metrics for pods from current run. was (Author: vietn): [^promgen-analytic-12hr.png] gives a snapshot of raw metrics tallies during a 12 hour run of 230 pods. Grafana dashboard url: http://hawkular-grafana-analytics.cloud2.jonqe.lab.eng.bos.redhat.com/das... (data may be pursed automatically after 14 days) Expected raw data points per 15 minute interval: 30 Observations: - As seen in the top graph raw metrics dip below 20 - there are metrics definitions but 0 data for some pods - I suspect the dips were caused by pod restarts but that is not the case. I randomly selected 2 pods, 1 with restart and 1 without restart and graph their data counts. Next step: - store metrics id by pod name as oppose to pod UID for easier cross references with output of oc commands - reduce the number of pod to see if there are still dips > Baseline #3 > ----------- > > Key: HAWKULARQE-81 > URL: https://issues.jboss.org/browse/HAWKULARQE-81 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: viet nguyen > Assignee: viet nguyen > Attachments: March28_0200_raw.zip, promgen-analytic-12hr.png > > > * Run pyme on master to eliminate vpn slowness > * Fix query start-end window > * Update pyme endpoint to increase metrics to 30 (currently 2) > * insert metrics tallies into a separate Hawkular Metrics instance and use Grafana as a visual tool -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 April 2017