March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2386) Legacy Kerberos in management, unable to configure fallback authentication.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2386?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2386: ------------------------------------- Fix Version/s: 3.0.0.Alpha24 (was: 3.0.0.Beta12) > Legacy Kerberos in management, unable to configure fallback authentication. > --------------------------------------------------------------------------- > > Key: WFCORE-2386 > URL: https://issues.jboss.org/browse/WFCORE-2386 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > Labels: regression > Fix For: 3.0.0.Alpha24 > > > In EAP 7.0 there was possible to configure fallback (e.g. BASIC) authentication, if client does not support SPNEGO authentication. In EAP 7.1 this feature does not work anymore. > In EAP 7.0 server returns multiple chalanges (Negotiate/Basic) and client could choose which he will use. > {code:title=EAP 7.0} > HTTP/1.1 401 Unauthorized > Connection: keep-alive > WWW-Authenticate: Negotiate > WWW-Authenticate: Basic realm="FallBackKerberosRealm" > X-Frame-Options: SAMEORIGIN > Content-Length: 77 > Content-Type: text/html > Date: Mon, 30 Jan 2017 11:02:45 GMT > <html><head><title>Error</title></head><body>401 - Unauthorized</body></html> > {code} > In EAP 7.1 (with same configuration) server returns only one chalange - Negotiate so client not supporting SPNEGO, can't fallback to Basic. > {code:title=EAP 7.1} > HTTP/1.1 401 Unauthorized > Connection: keep-alive > WWW-Authenticate: Negotiate > X-Frame-Options: SAMEORIGIN > Content-Length: 77 > Content-Type: text/html > Date: Mon, 30 Jan 2017 11:01:28 GMT > <html><head><title>Error</title></head><body>401 - Unauthorized</body></html> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2386) Legacy Kerberos in management, unable to configure fallback authentication.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2386?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-2386. -------------------------------------- Resolution: Done > Legacy Kerberos in management, unable to configure fallback authentication. > --------------------------------------------------------------------------- > > Key: WFCORE-2386 > URL: https://issues.jboss.org/browse/WFCORE-2386 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > Labels: regression > Fix For: 3.0.0.Alpha24 > > > In EAP 7.0 there was possible to configure fallback (e.g. BASIC) authentication, if client does not support SPNEGO authentication. In EAP 7.1 this feature does not work anymore. > In EAP 7.0 server returns multiple chalanges (Negotiate/Basic) and client could choose which he will use. > {code:title=EAP 7.0} > HTTP/1.1 401 Unauthorized > Connection: keep-alive > WWW-Authenticate: Negotiate > WWW-Authenticate: Basic realm="FallBackKerberosRealm" > X-Frame-Options: SAMEORIGIN > Content-Length: 77 > Content-Type: text/html > Date: Mon, 30 Jan 2017 11:02:45 GMT > <html><head><title>Error</title></head><body>401 - Unauthorized</body></html> > {code} > In EAP 7.1 (with same configuration) server returns only one chalange - Negotiate so client not supporting SPNEGO, can't fallback to Basic. > {code:title=EAP 7.1} > HTTP/1.1 401 Unauthorized > Connection: keep-alive > WWW-Authenticate: Negotiate > X-Frame-Options: SAMEORIGIN > Content-Length: 77 > Content-Type: text/html > Date: Mon, 30 Jan 2017 11:01:28 GMT > <html><head><title>Error</title></head><body>401 - Unauthorized</body></html> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1451) Unify/add unwrap methods to most of AttributeDefinition classes

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1451?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-1451: ----------------------------------- Assignee: (was: Tomaz Cerar) > Unify/add unwrap methods to most of AttributeDefinition classes > --------------------------------------------------------------- > > Key: WFCORE-1451 > URL: https://issues.jboss.org/browse/WFCORE-1451 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Tomaz Cerar > > we now have unwrap method only on StringListAD and PropertiesAD. but there are handful of others that should have it to if possible. > Thing to keep in mind is to make sure collection attributes can also return null as introduced in WFCORE-1448 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1451) Unify/add unwrap methods to most of AttributeDefinition classes

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1451?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1451: -------------------------------- Component/s: Domain Management > Unify/add unwrap methods to most of AttributeDefinition classes > --------------------------------------------------------------- > > Key: WFCORE-1451 > URL: https://issues.jboss.org/browse/WFCORE-1451 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > we now have unwrap method only on StringListAD and PropertiesAD. but there are handful of others that should have it to if possible. > Thing to keep in mind is to make sure collection attributes can also return null as introduced in WFCORE-1448 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-602) Ability to view an objects index of it's position in a list.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-602?page=com.atlassian.jira.plugin... ] Tomaz Cerar reassigned WFCORE-602: ---------------------------------- Assignee: (was: Tomaz Cerar) > Ability to view an objects index of it's position in a list. > ------------------------------------------------------------ > > Key: WFCORE-602 > URL: https://issues.jboss.org/browse/WFCORE-602 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darran Lofthouse > Labels: affects_elytron > > General improvements are being made to the management model for more fine grained manipulation of complex attributes, amongst these changes will be the ability to insert items at a specific position in a list. > This feature request is to ask for the ability to see an items index to identify it's position. > i.e. an end user can call :read-recource and see an items position without needing to count how many items there are in order to identify the position of the next insert. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBVFS-198) Correct or remove usage of finalize in VFS, TempDir, and TempFileProvider

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBVFS-198?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned JBVFS-198: --------------------------------- Assignee: (was: Tomaz Cerar) > Correct or remove usage of finalize in VFS, TempDir, and TempFileProvider > ------------------------------------------------------------------------- > > Key: JBVFS-198 > URL: https://issues.jboss.org/browse/JBVFS-198 > Project: JBoss VFS > Issue Type: Task > Reporter: Jason Greene > Fix For: 3.2.13.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1530) It should be possible to provide a 'per-cpu' value when configuring the task-max-threads attribute of a worker

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1530?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1530: -------------------------------- Component/s: IO > It should be possible to provide a 'per-cpu' value when configuring the task-max-threads attribute of a worker > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1530 > URL: https://issues.jboss.org/browse/WFCORE-1530 > Project: WildFly Core > Issue Type: Enhancement > Components: IO > Affects Versions: 2.1.0.Final > Reporter: Juan AMAT > Assignee: Tomaz Cerar > > We have an application running under JBoss EAP 6.4 and we are in the process to make it also run under Wildfly. > While doing performance testing we noticed that the number of threads that can process the incoming http requests was way lower in Wildfly. > Indeed we were using the 'default' worker and by default the max threads is set to 16 times the cpu count. In Jboss EAP the default configuration is 512 times the cpu count. > We were hitting this max and we did increase it. But then we had to provide an absolute value (and we would need to provide different values per type of servers). > It will be nicer to be able to configure instead a per-cpu value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1530) It should be possible to provide a 'per-cpu' value when configuring the task-max-threads attribute of a worker

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1530?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-1530: ----------------------------------- Assignee: (was: Tomaz Cerar) > It should be possible to provide a 'per-cpu' value when configuring the task-max-threads attribute of a worker > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1530 > URL: https://issues.jboss.org/browse/WFCORE-1530 > Project: WildFly Core > Issue Type: Enhancement > Components: IO > Affects Versions: 2.1.0.Final > Reporter: Juan AMAT > > We have an application running under JBoss EAP 6.4 and we are in the process to make it also run under Wildfly. > While doing performance testing we noticed that the number of threads that can process the incoming http requests was way lower in Wildfly. > Indeed we were using the 'default' worker and by default the max threads is set to 16 times the cpu count. In Jboss EAP the default configuration is 512 times the cpu count. > We were hitting this max and we did increase it. But then we had to provide an absolute value (and we would need to provide different values per type of servers). > It will be nicer to be able to configure instead a per-cpu value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6952) Provide way to display deployed application metadata

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6952?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-6952: --------------------------------- Assignee: (was: Stuart Douglas) > Provide way to display deployed application metadata > ---------------------------------------------------- > > Key: WFLY-6952 > URL: https://issues.jboss.org/browse/WFLY-6952 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Nicklas Karlsson > > It would be handy to have the deployment process print out the complete DeploymentInfo for an application so one could view the final order of filters and request listeners etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6952) Provide way to display deployed application metadata

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6952?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-6952: --------------------------------- Assignee: Stuart Douglas (was: Tomaz Cerar) > Provide way to display deployed application metadata > ---------------------------------------------------- > > Key: WFLY-6952 > URL: https://issues.jboss.org/browse/WFLY-6952 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Nicklas Karlsson > Assignee: Stuart Douglas > > It would be handy to have the deployment process print out the complete DeploymentInfo for an application so one could view the final order of filters and request listeners etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017