May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1547) SPNEGO: missing negstat field in the first reply for expired token

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1547?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1547: ---------------------------------- Fix Version/s: 1.4.0.CR1 > SPNEGO: missing negstat field in the first reply for expired token > ------------------------------------------------------------------ > > Key: ELY-1547 > URL: https://issues.jboss.org/browse/ELY-1547 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms, HTTP > Affects Versions: 1.2.4.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 1.3.1.Final, 1.4.0.CR1 > > > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1547) SPNEGO: missing negstat field in the first reply for expired token

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1547?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1547: ---------------------------------- Fix Version/s: 1.3.1.Final > SPNEGO: missing negstat field in the first reply for expired token > ------------------------------------------------------------------ > > Key: ELY-1547 > URL: https://issues.jboss.org/browse/ELY-1547 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms, HTTP > Affects Versions: 1.2.4.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 1.3.1.Final > > > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-200) B12 OpenShift Cluster is flaky

by Kevin Earls (JIRA)

Kevin Earls created SWSQE-200: --------------------------------- Summary: B12 OpenShift Cluster is flaky Key: SWSQE-200 URL: https://issues.jboss.org/browse/SWSQE-200 Project: Kiali QE Issue Type: QE Task Reporter: Kevin Earls Assignee: Michael Foley I'm opening this mostly as a placeholder, and will update it as I get more information on the problems I've been experiencing. Since I've been using B12 I've been experiencing more frequent failures than on other clusters, including minishift on my laptop and the CNCF CI Jenkins. Here are a couple of instances: 1. Deploying ElasticSearch along with the Jaeger Production templates requires allocating 2G or memory, even though the default 512M works fine elsewhere. This can be seen in the Jaeger Standalone Performance tests job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/J... . If you run the job without changing the ES_MEMORY parameter to 2Gi it will fail. 2. I have a set of smoke tests for Red Hat productized artifacts for the Jaeger Java client which are run using the Jaeger all-in-one template. It's fairly simple, but on B12 deployment of the Jaeger all-in-one images fails on every other build. I've made a copy of the job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/F... and its history should be clear. So far I have not been able to get any useful information about why this is failing. In the OpenShift console it looks like Jaeger has started correctly. There are no errors in the logs, nor any to be found under monitoring. But if you click on the Jaeger link, you get the message "Application is not available . The application is currently not serving requests at this endpoint. It may not have been started or is still starting." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3798) Upgrade WildFly Elytron to 1.3.1.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3798: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.3.1.Final Key: WFCORE-3798 URL: https://issues.jboss.org/browse/WFCORE-3798 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 5.0.0.Alpha5 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-197) QE needs to sign off of productized Jaeger builds

by Kevin Earls (JIRA)

[ https://issues.jboss.org/browse/SWSQE-197?page=com.atlassian.jira.plugin.... ] Kevin Earls commented on SWSQE-197: ----------------------------------- According to [~mfoley] the following steps should be taken: - List the testing you've done - Show summarized test results - Links to any supporting artifacts or evidence (such as Jenkins jobs, etc ...) - Links to other Jiras that support this sign-off - Communicate this Jira to the "other" team ... presumably Tiago ... and myself ... development, etc ... - Add this link to the Team Istio meeting document Mike, what section of the Istio meeting document should this go in? > QE needs to sign off of productized Jaeger builds > ------------------------------------------------- > > Key: SWSQE-197 > URL: https://issues.jboss.org/browse/SWSQE-197 > Project: Kiali QE > Issue Type: Epic > Reporter: Kevin Earls > Assignee: Kevin Earls > > This Epic is to track QE signoffs of productized Jaeger Builds -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1575) Release WildFly Elytron 1.3.1.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1575: ------------------------------------- Summary: Release WildFly Elytron 1.3.1.Final Key: ELY-1575 URL: https://issues.jboss.org/browse/ELY-1575 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.3.1.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-198) QE sign-off for Jaeger build 0.27.0

by Kevin Earls (JIRA)

[ https://issues.jboss.org/browse/SWSQE-198?page=com.atlassian.jira.plugin.... ] Kevin Earls commented on SWSQE-198: ----------------------------------- I've tested the 0.27.0.redhat-4 build from http://download-node-02.eng.bos.redhat.com/rcm-guest/staging/jaeger/jaege... and all tests pass. Results can be found here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/J... > QE sign-off for Jaeger build 0.27.0 > ----------------------------------- > > Key: SWSQE-198 > URL: https://issues.jboss.org/browse/SWSQE-198 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Kevin Earls > > See KIALI-640 for more details -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-34) The right bracket in prompt of workflow mode should be colorized by default color

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFWIP-34?page=com.atlassian.jira.plugin.s... ] Ingo Weiss commented on WFWIP-34: --------------------------------- Cool. Fixed on the latest PR update. > The right bracket in prompt of workflow mode should be colorized by default color > --------------------------------------------------------------------------------- > > Key: WFWIP-34 > URL: https://issues.jboss.org/browse/WFWIP-34 > Project: WildFly WIP > Issue Type: Bug > Reporter: Erich Duda > Assignee: Ingo Weiss > Labels: WFCORE-3577 > Attachments: screesnhot.png > > > !screesnhot.png|thumbnail! > As you can see on the screenshot, the right bracket in prompt is green what is {{workflow-color}} but it should be colored by default color as the left bracket. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10062) Application deployment fails with java.lang.NoClassDefFoundError: javax/enterprise/inject/Any$Literal

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-10062?page=com.atlassian.jira.plugin... ] Martin Kouba resolved WFLY-10062. --------------------------------- Resolution: Done > Application deployment fails with java.lang.NoClassDefFoundError: javax/enterprise/inject/Any$Literal > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-10062 > URL: https://issues.jboss.org/browse/WFLY-10062 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 12.0.0.Final > Reporter: Rich DiCroce > Assignee: Martin Kouba > Fix For: 13.0.0.Beta1 > > > Application fails to deploy with the below stack trace. EE8 preview mode is NOT enabled, which appears to be the cause. cdi-api-2.0.jar contains the class, but cdi-api-1.2.jar does not. > {quote} > 10:27:34,790 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."song-gaming-portal.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."song-gaming-portal.war".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_162] > Caused by: java.lang.NoClassDefFoundError: javax/enterprise/inject/Any$Literal > at org.jboss.weld.util.Observers.isContainerLifecycleObserverMethod(Observers.java:102) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final] > at org.jboss.weld.bootstrap.ExtensionBeanDeployer.createObserverMethod(ExtensionBeanDeployer.java:151) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final] > at org.jboss.weld.bootstrap.ExtensionBeanDeployer.createObserverMethods(ExtensionBeanDeployer.java:140) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final] > at org.jboss.weld.bootstrap.ExtensionBeanDeployer.deployBean(ExtensionBeanDeployer.java:101) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final] > at org.jboss.weld.bootstrap.ExtensionBeanDeployer.deployBeans(ExtensionBeanDeployer.java:75) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final] > at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:377) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final] > at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76) [weld-core-impl-3.0.3.Final.jar:3.0.3.Final] > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:95) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > ... 6 more > Caused by: java.lang.ClassNotFoundException: javax.enterprise.inject.Any$Literal from [Module "org.jboss.weld.core" from local module loader @2ea6137 (finder: local module finder @41ee392b (roots: D:\wildfly\wildfly-12.0.0.Final-GP\modules,D:\wildfly\wildfly-12.0.0.Final-GP\modules\system\layers\base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:199) [jboss-modules.jar:1.7.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) [jboss-modules.jar:1.7.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) [jboss-modules.jar:1.7.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) [jboss-modules.jar:1.7.0.Final] > ... 16 more > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3789) Unable to pass any attribute to jboss-cli.ps1 script

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3789?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3789: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3246 > Unable to pass any attribute to jboss-cli.ps1 script > ---------------------------------------------------- > > Key: WFCORE-3789 > URL: https://issues.jboss.org/browse/WFCORE-3789 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Scripts > Reporter: Tomas Terem > Assignee: Jean-Francois Denise > > Unable to pass any attribute to jboss-cli.ps1 script > {noformat} > C:\wildfly\wildfly-12.0.0.Final\bin> PowerShell -ExecutionPolicy Bypass -File jboss-cli.ps1 --help > '--help-Dcom.ibm.jsse2.overrideDefaultTLS=true' is not a valid operation name. > C:\wildfly\wildfly-12.0.0.Final\bin> PowerShell -ExecutionPolicy Bypass -File jboss-cli.ps1 --version > '--version-Dcom.ibm.jsse2.overrideDefaultTLS=true' is not a valid operation name > . > C:\wildfly\wildfly-12.0.0.Final\bin> PowerShell -ExecutionPolicy Bypass -File jboss-cli.ps1 -c > '-c-Dcom.ibm.jsse2.overrideDefaultTLS=true' is not a valid operation name. > C:\wildfly\wildfly-12.0.0.Final\bin> PowerShell -ExecutionPolicy Bypass -File jboss-cli.ps1 > You are disconnected at the moment. Type 'connect' to connect to the server or ' > help' for the list of supported commands. > [disconnected /] > {noformat} > I am using PowerShell 4.0 > {noformat} > PS C:\> $PSVersionTable.PSVersion > Major Minor Build Revision > ----- ----- ----- -------- > 4 0 -1 -1 > PS C:\> > {noformat} > This behaviour is caused by this change: > https://github.com/wildfly/wildfly-core/blame/master/core-feature-pack/sr... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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