May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3878) Make implementing the org.wildfly.extension.elytron.Configurable optional for configurable components.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3878: ---------------------------------------- Summary: Make implementing the org.wildfly.extension.elytron.Configurable optional for configurable components. Key: WFCORE-3878 URL: https://issues.jboss.org/browse/WFCORE-3878 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Darran Lofthouse Assignee: Martin Mazanek Fix For: 6.0.0.Alpha1 Presently custom components within the Elytron subsystem are required to implement the 'org.wildfly.extension.elytron.Configurable' interface if they wish to support receiving a Map of configuration Strings. This means that the custom component needs to depend on both the WildFly Elytron project and the subsystem. It should be possible for components to add the following method without implementing the interface and be configurable. {noformat} void initialize(final Map<String, String> configuration); {noformat} We also have a long standing issue in that if we add a new component to WildFly Elytron it can not be used until we can add a resource to configure it. By supporting configurable custom components without needing a dependency on the subsystem new components added to WildFly Elytron could be usable whilst the subsystem definitions catch up. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3877) Make implementing the org.wildfly.extension.elytron.Configurable optional for configurable components.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3877: ---------------------------------------- Summary: Make implementing the org.wildfly.extension.elytron.Configurable optional for configurable components. Key: WFCORE-3877 URL: https://issues.jboss.org/browse/WFCORE-3877 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Darran Lofthouse Assignee: Martin Mazanek Fix For: 6.0.0.Alpha1 Presently custom components within the Elytron subsystem are required to implement the 'org.wildfly.extension.elytron.Configurable' interface if they wish to support receiving a Map of configuration Strings. This means that the custom component needs to depend on both the WildFly Elytron project and the subsystem. It should be possible for components to add the following method without implementing the interface and be configurable. {noformat} void initialize(final Map<String, String> configuration); {noformat} We also have a long standing issue in that if we add a new component to WildFly Elytron it can not be used until we can add a resource to configure it. By supporting configurable custom components without needing a dependency on the subsystem new components added to WildFly Elytron could be usable whilst the subsystem definitions catch up. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-249) Update recent kiali Ui changes in python GUI automation

by Jeeva Kandasamy (JIRA)

Jeeva Kandasamy created SWSQE-249: ------------------------------------- Summary: Update recent kiali Ui changes in python GUI automation Key: SWSQE-249 URL: https://issues.jboss.org/browse/SWSQE-249 Project: Kiali QE Issue Type: QE Task Reporter: Jeeva Kandasamy Assignee: Jeeva Kandasamy I see big changes in Istio mixer page(now istio config page). Update this PR: https://github.com/Kiali-QE/kiali-qe-python/pull/33 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-248) Update kiali rest python client

by Jeeva Kandasamy (JIRA)

Jeeva Kandasamy created SWSQE-248: ------------------------------------- Summary: Update kiali rest python client Key: SWSQE-248 URL: https://issues.jboss.org/browse/SWSQE-248 Project: Kiali QE Issue Type: QE Task Reporter: Jeeva Kandasamy Assignee: Jeeva Kandasamy Update kiali python client[1], changes are available here [2] [1] - https://github.com/Kiali-QE/kiali-client-python [2] - https://github.com/kiali/kiali/blob/master/routing/routes.go -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3876) Composite operation on filesystem-realm blocks management operations

by Claudio Miranda (JIRA)

Claudio Miranda created WFCORE-3876: --------------------------------------- Summary: Composite operation on filesystem-realm blocks management operations Key: WFCORE-3876 URL: https://issues.jboss.org/browse/WFCORE-3876 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Claudio Miranda Assignee: Darran Lofthouse There is a problem when adding an identity and an attribute on filesystem-realm as composite operation, it blocks the operation, but also blocks some other operations, for example, while the composite operation run, the other following operations just blocks. This problem only occurs in domain mode. The filesystem-realm=file1 was created with no errors. Add an identity and a identity attribute as composite operation {code} batch /host=master/server=server-three/subsystem=elytron/filesystem-realm=file1:add-identity(identity=user3) /host=master/server=server-three/subsystem=elytron/filesystem-realm=file1:add-identity-attribute(identity=user3,name=key1,value=[val1,val11]) run-batch {code} The following composite, also blocks the same way (for an existing identity named user3) {code} batch /host=master/server=server-three/subsystem=elytron/filesystem-realm=file1:add-identity-attribute(identity=user3,name=key3,value=[val3,val33]) /host=master/server=server-three/subsystem=elytron/filesystem-realm=file1:add-identity-attribute(identity=user3,name=key4,value=[val4,val44]) run-batch {code} The following operation just blocks waiting the above operation to finish. {code} /host=master/server=server-three/subsystem=elytron/filesystem-realm=file1:read-identity(identity=other) {code} {code} /profile=full-ha/subsystem=elytron/filesystem-realm=file3:add(path=file3) {code} {code} /profile=full-ha/subsystem=elytron/properties-realm=props1:add(users-properties={path=application-users.properties,relative-to=jboss.domain.config.dir,digest-realm-name=ApplicationRealm}) {code} It also blocks write-attribute operation on other subsystems {code} /profile=full-ha/subsystem=io/worker=default:write-attribute(name=task-max-threads,value=100) /profile=full-ha/subsystem=datasources/data-source=ExampleDS:write-attribute(name=max-pool-size,value=12) {code} The last operation reports as a non-progressing operation {code} /host=master/core-service=management/service=management-operations:find-non-progressing-operation { "outcome" => "success", "result" => "500616352" } [domain@localhost:9990 /] /host=master/core-service=management/service=management-operations/active-operation=*:read-resource { "outcome" => "success", "result" => [ { "address" => [ ("host" => "master"), ("core-service" => "management"), ("service" => "management-operations"), ("active-operation" => "-886331830") ], "outcome" => "success", "result" => { "access-mechanism" => "NATIVE", "address" => [ ("host" => "master"), ("core-service" => "management"), ("service" => "management-operations"), ("active-operation" => "*") ], "caller-thread" => "management-handler-thread - 15", "cancelled" => false, "domain-rollout" => false, "domain-uuid" => undefined, "exclusive-running-time" => -1L, "execution-status" => "executing", "operation" => "read-resource", "running-time" => 2341554L } }, { "address" => [ ("host" => "master"), ("core-service" => "management"), ("service" => "management-operations"), ("active-operation" => "-199839257") ], "outcome" => "success", "result" => { "access-mechanism" => "NATIVE", "address" => [], "caller-thread" => "management-handler-thread - 13", "cancelled" => false, "domain-rollout" => false, "domain-uuid" => undefined, "exclusive-running-time" => -1L, "execution-status" => "executing", "operation" => "composite", "running-time" => 37961295588L } }, { "address" => [ ("host" => "master"), ("core-service" => "management"), ("service" => "management-operations"), ("active-operation" => "500616352") ], "outcome" => "success", "result" => { "access-mechanism" => "NATIVE", "address" => [ ("profile" => "full-ha"), ("subsystem" => "io"), ("worker" => "default") ], "caller-thread" => "management-handler-thread - 14", "cancelled" => false, "domain-rollout" => false, "domain-uuid" => "87a864ef-e287-4436-acd5-4842459dfc2e", "exclusive-running-time" => 33671893306L, "execution-status" => "executing", "operation" => "write-attribute", "running-time" => 33671782128L } } ] } {code} After the operation timeout, the second step of the composite operation as error. {code} The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: Step: step-2 Operation: /host=master/server=server-three/subsystem=elytron/filesystem-realm=file1:add-identity-attribute(identity=user3,name=key1,value=[val1,val11]) Failure: WFLYCTL0409: Execution of operation 'add-identity-attribute' on remote process at address '[ ("host" => "master"), ("server" => "server-three") ]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation {code} I understand that to add the identity attribute, it should run as non composite, and it works, but the problem is the blocking it does on the other operations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3872) Upgrade to WildFly Galleon plugins 1.0.0.CR9 and fork embedded in the build

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3872?page=com.atlassian.jira.plugi... ] Alexey Loubyansky updated WFCORE-3872: -------------------------------------- Description: 1.0.0.CR9 significantly reduces the classpath prepared by the plugins to launch the embedded server and also adds an option to execute the embedded in a separate process to avoid FD leaks in jboss-modules. (was: 1.0.0.CR7 significantly reduces the classpath prepared by the plugins to launch the embedded server and also adds an option to execute the embedded in a separate process to avoid FD leaks in jboss-modules.) Summary: Upgrade to WildFly Galleon plugins 1.0.0.CR9 and fork embedded in the build (was: Upgrade to WildFly Galleon plugins 1.0.0.CR7 and fork embedded in the build) > Upgrade to WildFly Galleon plugins 1.0.0.CR9 and fork embedded in the build > --------------------------------------------------------------------------- > > Key: WFCORE-3872 > URL: https://issues.jboss.org/browse/WFCORE-3872 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > 1.0.0.CR9 significantly reduces the classpath prepared by the plugins to launch the embedded server and also adds an option to execute the embedded in a separate process to avoid FD leaks in jboss-modules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1589) elytron-client-1_1.xsd is invalid

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1589?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1589: ---------------------------- Priority: Critical (was: Major) > elytron-client-1_1.xsd is invalid > --------------------------------- > > Key: ELY-1589 > URL: https://issues.jboss.org/browse/ELY-1589 > Project: WildFly Elytron > Issue Type: Bug > Components: XML > Affects Versions: 1.3.2.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > > XSD validation of test-wildfly-config.xml in tests fails because of invalid XSD: > {noformat}Src-resolve: Cannot Resolve The Name 'resource-type' To A(n) 'simpleType Definition' Component.{noformat} > Problem is, "resource-type" (which is complexType) is used as type of an attribute (not of an element) in certificate-revocation-list-type. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1589) elytron-client-1_1.xsd is invalid

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1589?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1589: ---------------------------- Description: XSD validation of test-wildfly-config.xml in tests fails because of invalid XSD: {noformat}Src-resolve: Cannot Resolve The Name 'resource-type' To A(n) 'simpleType Definition' Component.{noformat} Problem is, "resource-type" (which is complexType) is used as type of an attribute (not of an element) in certificate-revocation-list-type. Edit: there is much more errors when trying to verify testing XMLs against XSDs. was: XSD validation of test-wildfly-config.xml in tests fails because of invalid XSD: {noformat}Src-resolve: Cannot Resolve The Name 'resource-type' To A(n) 'simpleType Definition' Component.{noformat} Problem is, "resource-type" (which is complexType) is used as type of an attribute (not of an element) in certificate-revocation-list-type. > elytron-client-1_1.xsd is invalid > --------------------------------- > > Key: ELY-1589 > URL: https://issues.jboss.org/browse/ELY-1589 > Project: WildFly Elytron > Issue Type: Bug > Components: XML > Affects Versions: 1.3.2.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > > XSD validation of test-wildfly-config.xml in tests fails because of invalid XSD: > {noformat}Src-resolve: Cannot Resolve The Name 'resource-type' To A(n) 'simpleType Definition' Component.{noformat} > Problem is, "resource-type" (which is complexType) is used as type of an attribute (not of an element) in certificate-revocation-list-type. > Edit: there is much more errors when trying to verify testing XMLs against XSDs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-247) Add kiali route check in checker script

by Sunil kondkar (JIRA)

Sunil kondkar created SWSQE-247: ----------------------------------- Summary: Add kiali route check in checker script Key: SWSQE-247 URL: https://issues.jboss.org/browse/SWSQE-247 Project: Kiali QE Issue Type: Sub-task Reporter: Sunil kondkar Assignee: Michael Foley Add kiali route check in checker script and use curl to validate that the URL is accessible curl --insecure https://admin:admin@kiali-istio-system.ose.os39-kiali.osoos.centralci.eng... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-247) Add kiali route check in checker script

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/SWSQE-247?page=com.atlassian.jira.plugin.... ] Sunil kondkar reassigned SWSQE-247: ----------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > Add kiali route check in checker script > --------------------------------------- > > Key: SWSQE-247 > URL: https://issues.jboss.org/browse/SWSQE-247 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > > Add kiali route check in checker script and use curl to validate that the URL is accessible > curl --insecure https://admin:admin@kiali-istio-system.ose.os39-kiali.osoos.centralci.eng... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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