March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11697) WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11697?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFLY-11697: ------------------------------------ Summary: WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL (was: WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL) > WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL > ----------------------------------------------------------------------------------- > > Key: WFLY-11697 > URL: https://issues.jboss.org/browse/WFLY-11697 > Project: WildFly > Issue Type: Feature Request > Components: REST, Security, Web Services > Affects Versions: 16.0.0.Final > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > This feature request is about making use of authentication configuration on the client side of the WS / REST deployment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11810) Fix 'org.jboss.msc.Service' API to enable proper service installation

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-11810?page=com.atlassian.jira.plugin... ] Jan Stourac commented on WFLY-11810: ------------------------------------ I want to mention also WFLY-11387 here, although based on the provided fix, that was probably a different issue with different root-cause to what this issue is aimed at. So just for a reference... > Fix 'org.jboss.msc.Service' API to enable proper service installation > --------------------------------------------------------------------- > > Key: WFLY-11810 > URL: https://issues.jboss.org/browse/WFLY-11810 > Project: WildFly > Issue Type: Bug > Components: MSC > Affects Versions: 16.0.0.Final > Reporter: Jan Stourac > Assignee: Jeff Mesnil > Priority: Major > > I have no necessary insight regarding to the code but based on the discussion in WFLY-11603 ([comment|https://issues.jboss.org/browse/WFLY-11603?focusedCommentId=13687...]) it is not possible to use 'org.jboss.msc.Service' API to properly install service and deprecated 'org.jboss.msc.service.Service' API has to be used instead. > It is necessary to fix the behavior of the new API so when we switch to it, we don't introduce the issue described and fixed in WFLY-11603 again. As it was an intermittent NPE, there is a risk that during the simple switch from deprecated API the introduced issue is not caught right-away but after some time... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11810) Fix 'org.jboss.msc.Service' API to enable proper service installation

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-11810?page=com.atlassian.jira.plugin... ] Jan Stourac reassigned WFLY-11810: ---------------------------------- Assignee: Jeff Mesnil > Fix 'org.jboss.msc.Service' API to enable proper service installation > --------------------------------------------------------------------- > > Key: WFLY-11810 > URL: https://issues.jboss.org/browse/WFLY-11810 > Project: WildFly > Issue Type: Bug > Components: MSC > Affects Versions: 16.0.0.Final > Reporter: Jan Stourac > Assignee: Jeff Mesnil > Priority: Major > > I have no necessary insight regarding to the code but based on the discussion in WFLY-11603 ([comment|https://issues.jboss.org/browse/WFLY-11603?focusedCommentId=13687...]) it is not possible to use 'org.jboss.msc.Service' API to properly install service and deprecated 'org.jboss.msc.service.Service' API has to be used instead. > It is necessary to fix the behavior of the new API so when we switch to it, we don't introduce the issue described and fixed in WFLY-11603 again. As it was an intermittent NPE, there is a risk that during the simple switch from deprecated API the introduced issue is not caught right-away but after some time... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11810) Fix 'org.jboss.msc.Service' API to enable proper service installation

by Jan Stourac (Jira)

Jan Stourac created WFLY-11810: ---------------------------------- Summary: Fix 'org.jboss.msc.Service' API to enable proper service installation Key: WFLY-11810 URL: https://issues.jboss.org/browse/WFLY-11810 Project: WildFly Issue Type: Bug Components: MSC Affects Versions: 16.0.0.Final Reporter: Jan Stourac I have no necessary insight regarding to the code but based on the discussion in WFLY-11603 ([comment|https://issues.jboss.org/browse/WFLY-11603?focusedCommentId=13687...]) it is not possible to use 'org.jboss.msc.Service' API to properly install service and deprecated 'org.jboss.msc.service.Service' API has to be used instead. It is necessary to fix the behavior of the new API so when we switch to it, we don't introduce the issue described and fixed in WFLY-11603 again. As it was an intermittent NPE, there is a risk that during the simple switch from deprecated API the introduced issue is not caught right-away but after some time... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1049) Add equivalent @WebContext for JAX-RS?

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-1049?page=com.atlassian.jira.plugin.... ] Marek Kopecký commented on WFLY-1049: ------------------------------------- [~ron_sigal]: There is no activity for ~6 years. What is your plan with this feature request? Reject? > Add equivalent @WebContext for JAX-RS? > -------------------------------------- > > Key: WFLY-1049 > URL: https://issues.jboss.org/browse/WFLY-1049 > Project: WildFly > Issue Type: Feature Request > Components: REST > Reporter: Fernando Rubbo > Priority: Major > Labels: BASIC_AUTH, FORM_AUTH, JAX-RS, > > Currently, in our application we use @WebContext to set a different contextRoot for JAX-WS. For example: > > {code:java} > @Stateless > @SecurityDomain("test2") > @WebService(name = "HelloSoap", portName = "HelloSoapPort", serviceName = "HelloSoap", targetNamespace = "http://com.test") > @WebContext(contextRoot = "/ws", urlPattern = "/HelloSoap", secureWSDLAccess = false, authMethod = "BASIC", transportGuarantee = "NONE") > public class HelloSoap { ... } > {code} > We would like to have an equivalent annotation for JAX-RS? It is required whenever a web app uses FORM_AUTH and there exists web services (JAX-WS and JAX-RS), inside of the same package, using as BASIC_AUTH. > > Thankyou in advance, > Fernando Rubbo -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4621) RESTEasy SMIME doesn't work with WildFly current module setup

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-4621?page=com.atlassian.jira.plugin.... ] Marek Kopecký commented on WFLY-4621: ------------------------------------- [~ron_sigal] (cc [~weinanli]): I'm unable to run example from the description of this jira, but both linked PRs are merged. What is the status of this jira? Should this be resolved? There is no activity on this jira for ~3.5 years. > RESTEasy SMIME doesn't work with WildFly current module setup > ------------------------------------------------------------- > > Key: WFLY-4621 > URL: https://issues.jboss.org/browse/WFLY-4621 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 9.0.0.CR1 > Reporter: Weinan Li > Assignee: Weinan Li > Priority: Major > Attachments: patch_WFLY-4621_all, patch_WFLY-4621_new > > > RESTEasy provides the functions of SMIME encryption and here is an example that can be deployed into WildFly: > https://github.com/liweinan/digital-signatures/tree/master/smime > And currently resteasy-crypto module doesn't work properly in WildFly unless applied the following patch: > {code:diff} > power:modules weinanli$ git diff > warning: LF will be replaced by CRLF in system/layers/base/org/bouncycastle/main/module.xml. > The file will have its original line endings in your working directory. > diff --git a/system/layers/base/org/bouncycastle/main/module.xml b/system/layers/base/org/bouncycastle/main/module.xml > index 5d13395..83ae97c 100644 > --- a/system/layers/base/org/bouncycastle/main/module.xml > +++ b/system/layers/base/org/bouncycastle/main/module.xml > @@ -24,12 +24,17 @@ > <module xmlns="urn:jboss:module:1.3" name="org.bouncycastle"> > <resources> > +  > + <resource-root path="bcprov-jdk16-1.46.jar"/> > + <resource-root path="bcmail-jdk16-1.46.jar"/> > <resource-root path="bcpkix-jdk15on-1.52.jar"/> > </resources> > <dependencies> > <module name="javax.api"/> > + <module name="javax.mail.api"/> > + <module name="javax.activation.api"/> > </dependencies> > - > </module> > {code} > After applying the above patch then the example can pass all the tests: > {code} > power:smime weinanli$ mvn -q clean package > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 > power:smime weinanli$ mvn -q wildfly:deploy > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 > May 11, 2015 9:24:27 PM org.xnio.Xnio <clinit> > INFO: XNIO version 3.3.0.Final > May 11, 2015 9:24:27 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.3.0.Final > May 11, 2015 9:24:27 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 4.0.7.Final > power:smime weinanli$ mvn -q integration-test > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.jboss.resteasy.tests.smime.SMIMETest > Encrypted Message From Server: > Customer{name='Bill'} > Signed Message From Server: > Customer{name='Bill'} > Customer{name='Bill'} > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 sec - in org.jboss.resteasy.tests.smime.SMIMETest > Results : > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 > power:smime weinanli$ > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-625) Get access for kiali qe to https://gitlab.cee.redhat.com/istio

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-625?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-625: -------------------------------- Description: We agreed that we want to share one organization among istio and kiali in cee gitlab. Note that there is already https://gitlab.cee.redhat.com/kiali-qe/ was:We agreed that we want to share one organization among istio and kiali in cee gitlab. > Get access for kiali qe to https://gitlab.cee.redhat.com/istio > -------------------------------------------------------------- > > Key: SWSQE-625 > URL: https://issues.jboss.org/browse/SWSQE-625 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > We agreed that we want to share one organization among istio and kiali in cee gitlab. > Note that there is already https://gitlab.cee.redhat.com/kiali-qe/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-626) Investigate options to share docker registry with istio team

by Filip Brychta (Jira)

Filip Brychta created SWSQE-626: ----------------------------------- Summary: Investigate options to share docker registry with istio team Key: SWSQE-626 URL: https://issues.jboss.org/browse/SWSQE-626 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Tiago runs his docker registry in Central CI We run our registry in b22 ocp cluster. Do we want to run just one registry? What would be content: * product images * jenkins slaves images * ?? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-625) Get access for kiali qe to https://gitlab.cee.redhat.com/istio

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-625?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-625: -------------------------------- Issue Type: Task (was: Bug) > Get access for kiali qe to https://gitlab.cee.redhat.com/istio > -------------------------------------------------------------- > > Key: SWSQE-625 > URL: https://issues.jboss.org/browse/SWSQE-625 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > We agreed that we want to share one organization among istio and kiali in cee gitlab. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11809) RBAC: Deployment button not available for server group scoped role.

by Eugen Pribulla (Jira)

[ https://issues.jboss.org/browse/WFLY-11809?page=com.atlassian.jira.plugin... ] Eugen Pribulla updated WFLY-11809: ---------------------------------- Steps to Reproduce: * Install Wildfly 16.0.0.Final. * Enable RBAC with admin as SuperUser. * Create new server group scoped role *MainGroupDeployer* based on role *Deployer* scoped to *main-server-group*. * Create new management user *test* and assign *MainGroupDeployer* to it. * Login to HAL console as user *test*. * Select from menu "Deployments" -> "Server Groups" -> "main-server-group" * Deployment button on top of the ServerGroupDeployment column should be visible but isn't. was: * Install Wildfly 16.0.0.Final. * Enable RBAC with admin as SuperUser. * Create new server group scoped role *MainGroupDeployer* based on role *Deployer* scoped to *main-server-group*. * Create new management user *test* and assign *MainGroupDeployer* to it. * Login to HAL console as user *test*. * Select from menu "Deployments" -> "Server Groups" -> "main-server-group" * Deployment button on top of ServerGroupDeployment column should be visible but isn't. > RBAC: Deployment button not available for server group scoped role. > ------------------------------------------------------------------- > > Key: WFLY-11809 > URL: https://issues.jboss.org/browse/WFLY-11809 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 16.0.0.Final > Environment: Windows 10 x64 > Reporter: Eugen Pribulla > Assignee: Harald Pehl > Priority: Major > > RBAC security enabled. > If you create a new server group scoped role (Deployer as base) then deployment buttons in the ServerGroupDeploymentColumn are hidden for that role. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019