May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9702) SSO Integration for Programmatic Authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9702?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-9702: ----------------------------------- Issue Type: Feature Request (was: Bug) > SSO Integration for Programmatic Authentication > ----------------------------------------------- > > Key: WFLY-9702 > URL: https://issues.jboss.org/browse/WFLY-9702 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Security, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > > At the moment the SSO integration only fully covers authentication mechanisms as they can be wrapped, we need to revisit for programmatic authentication. > In this scenario we don't have either a wrapped mechanism or a CallbackHandler. > Couple of options: - > * Can we get away with pushing in some form of IdentityCache factory the mechs can obtain from the request? This may miss the additional notifications the SSO impl depends on. > * Can we also better support listening for the notifications without the need for wrappers? This could cover both mechs and programmatic authentication? > * Instead do we make the programmatic authenticator pluggable, i.e. push in an SSO aware impl, it can choose how to handle it's own caching and also doesn't need the notifications as it is in control of that stage of the process. > * -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10471) Rework mod_cluster load provider into proper resources

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-10471: ------------------------------------- Summary: Rework mod_cluster load provider into proper resources Key: WFLY-10471 URL: https://issues.jboss.org/browse/WFLY-10471 Project: WildFly Issue Type: Task Components: mod_cluster Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Optional Follow up on WFLY-8364. It would be ideal if this was reworked into correct resources, like the following: {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} {{/subsystem=modcluster/proxy=default/load-provider=simple}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10471) Rework mod_cluster load provider into proper resources

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10471?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10471: ---------------------------------- Affects Version/s: 13.0.0.Beta1 > Rework mod_cluster load provider into proper resources > ------------------------------------------------------ > > Key: WFLY-10471 > URL: https://issues.jboss.org/browse/WFLY-10471 > Project: WildFly > Issue Type: Task > Components: mod_cluster > Affects Versions: 13.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > Follow up on WFLY-8364. It would be ideal if this was reworked into correct resources, like the following: > {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} > {{/subsystem=modcluster/proxy=default/load-provider=simple}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8364) mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8364?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8364: --------------------------------- Description: {code} <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> <mod-cluster-config advertise-socket="modcluster" connector="ajp"> <simple-load-provider factor="5"/> <dynamic-load-provider> <load-metric type="cpu"/> </dynamic-load-provider> </mod-cluster-config> </subsystem> {code} However, it would be ideal if this was reworked into correct resources, like the following: {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} {{/subsystem=modcluster/proxy=default/load-provider=simple}} was: {code} <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> <mod-cluster-config advertise-socket="modcluster" connector="ajp"> <simple-load-provider factor="5"/> <dynamic-load-provider> <load-metric type="cpu"/> </dynamic-load-provider> </mod-cluster-config> </subsystem> {code} > mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-8364 > URL: https://issues.jboss.org/browse/WFLY-8364 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > {code} > <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> > <mod-cluster-config advertise-socket="modcluster" connector="ajp"> > <simple-load-provider factor="5"/> > <dynamic-load-provider> > <load-metric type="cpu"/> > </dynamic-load-provider> > </mod-cluster-config> > </subsystem> > {code} > However, it would be ideal if this was reworked into correct resources, like the following: > {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} > {{/subsystem=modcluster/proxy=default/load-provider=simple}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8364) mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8364?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8364: --------------------------------- Description: {code} <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> <mod-cluster-config advertise-socket="modcluster" connector="ajp"> <simple-load-provider factor="5"/> <dynamic-load-provider> <load-metric type="cpu"/> </dynamic-load-provider> </mod-cluster-config> </subsystem> {code} However, it would be ideal if this was reworked into correct resources, like the following: {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} {{/subsystem=modcluster/proxy=default/load-provider=simple}} Jira for that TBD. was: {code} <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> <mod-cluster-config advertise-socket="modcluster" connector="ajp"> <simple-load-provider factor="5"/> <dynamic-load-provider> <load-metric type="cpu"/> </dynamic-load-provider> </mod-cluster-config> </subsystem> {code} However, it would be ideal if this was reworked into correct resources, like the following: {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} {{/subsystem=modcluster/proxy=default/load-provider=simple}} > mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-8364 > URL: https://issues.jboss.org/browse/WFLY-8364 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > {code} > <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> > <mod-cluster-config advertise-socket="modcluster" connector="ajp"> > <simple-load-provider factor="5"/> > <dynamic-load-provider> > <load-metric type="cpu"/> > </dynamic-load-provider> > </mod-cluster-config> > </subsystem> > {code} > However, it would be ideal if this was reworked into correct resources, like the following: > {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} > {{/subsystem=modcluster/proxy=default/load-provider=simple}} > Jira for that TBD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10470) Upgrade WildFly Core 5.0.0.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-10470: ---------------------------------- Summary: Upgrade WildFly Core 5.0.0.Final Key: WFLY-10470 URL: https://issues.jboss.org/browse/WFLY-10470 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 13.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-270) Document usage of jenkins docker slaves

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-270: ----------------------------------- Summary: Document usage of jenkins docker slaves Key: SWSQE-270 URL: https://issues.jboss.org/browse/SWSQE-270 Project: Kiali QE Issue Type: Task Reporter: Filip Brychta Assignee: Michael Foley It would be nice to have documentation describing available slaves, labes, usage of sudo etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-270) Document usage of jenkins docker slaves

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-270?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-270: -------------------------------- Sprint: Kiali QE Sprint 6 > Document usage of jenkins docker slaves > --------------------------------------- > > Key: SWSQE-270 > URL: https://issues.jboss.org/browse/SWSQE-270 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Michael Foley > > It would be nice to have documentation describing available slaves, labes, usage of sudo etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-269) Create new docker image for PR jobs

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-269?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy closed SWSQE-269. --------------------------------- Resolution: Done I forget about sudo access. Closing this ticket. > Create new docker image for PR jobs > ----------------------------------- > > Key: SWSQE-269 > URL: https://issues.jboss.org/browse/SWSQE-269 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Currently, PR jobs are using kiali-qe-python Jenkins slave docker images. UI tests docker images needs to be isolated. > Create new Jenkins slave docker image for PR jobs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3724) stop-servers following by a reload operation could end up in a long period with an unmanageable domain

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3724?page=com.atlassian.jira.plugi... ] Yeray Borges closed WFCORE-3724. -------------------------------- Resolution: Won't Fix > stop-servers following by a reload operation could end up in a long period with an unmanageable domain > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3724 > URL: https://issues.jboss.org/browse/WFCORE-3724 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Affects Versions: 5.0.0.Alpha2 > Reporter: Yeray Borges > Assignee: Yeray Borges > > When {{:stop-servers}} operation is used with a timeout different than 0, a graceful stop is performed on each server. > If the user executes {{/host=master:reload}} in a DC, the reload operation waits for the servers until they are completely stopped. This could be an issue for a DC since the user is unable to execute any operation meanwhile the reload op is waiting for the previous stop. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 May 2018