April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1075) Provide a utility to track and query the principal from a SASL client authentication

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1075?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved ELY-1075. ------------------------------ Resolution: Done > Provide a utility to track and query the principal from a SASL client authentication > ------------------------------------------------------------------------------------ > > Key: ELY-1075 > URL: https://issues.jboss.org/browse/ELY-1075 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta37 > > > The client needs to be able to discover what its authentication principal is. The server does not always share that information. So, we need a way to derive the authentication principal from the authorization ID, callbacks, mechanism, and/or external identity. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8448) Upgrade JBoss Metadata from 10.0.0.Final to 10.0.2.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-8448?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-8448: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9855, https://github.com/wildfly/wildfly/pull/9936 (was: https://github.com/wildfly/wildfly/pull/9855) > Upgrade JBoss Metadata from 10.0.0.Final to 10.0.2.Final > -------------------------------------------------------- > > Key: WFLY-8448 > URL: https://issues.jboss.org/browse/WFLY-8448 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5546) The flushOnSessionInvalidation is not parsed correctly from jboss-web.xml

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-5546?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-5546: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9936 (was: https://github.com/wildfly/wildfly/pull/8771) > The flushOnSessionInvalidation is not parsed correctly from jboss-web.xml > ------------------------------------------------------------------------- > > Key: WFLY-5546 > URL: https://issues.jboss.org/browse/WFLY-5546 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR3 > Reporter: Josef Cacek > Assignee: Ivo Studensky > > The class {{org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser}} doesn't support reading {{"flushOnSessionInvalidation"}} attribute on {{"security-domain"}} element. And also the schema files for {{jboss-web.xml}} doesn't mention this attribute. > The class {{org.jboss.metadata.web.jboss.JBossWebMetaData}} contains the attribute {{flushOnSessionInvalidation}}, which comes from old JBoss versions (3.2 and 4.0). [The description|https://developer.jboss.org/wiki/CachingLoginCredentials] says: > ??The jboss-web.xml security-domain element now supports a flushOnSessionInvalidation boolean attribute that when true, will flush the security-domain JAAS authentication cache for the associated user principal.?? > This attribute is also supported in WildFly integration with Undertow ([look at source|https://github.com/wildfly/wildfly/blob/10.0.0.CR3/undertow/src/ma...]), but the code is never reached as the flushOnSessionInvalidation attribute value stays always *false*. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8448) Upgrade JBoss Metadata from 10.0.0.Final to 10.0.2.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-8448?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-8448: -------------------------------- Summary: Upgrade JBoss Metadata from 10.0.0.Final to 10.0.2.Final (was: Upgrade JBoss Metadata from 10.0.0.Final to 10.0.1.Final) > Upgrade JBoss Metadata from 10.0.0.Final to 10.0.2.Final > -------------------------------------------------------- > > Key: WFLY-8448 > URL: https://issues.jboss.org/browse/WFLY-8448 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2673) HTTP redirect if both http and https socket-binding is configured for http-interface

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFCORE-2673: ------------------------------------ Summary: HTTP redirect if both http and https socket-binding is configured for http-interface Key: WFCORE-2673 URL: https://issues.jboss.org/browse/WFCORE-2673 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Ondrej Lukas Assignee: Brian Stansberry In case when both http and https socket-binding is configured for management http-interface and http port is accessed then server tries to redirect automatically to https port. Access http is not possible. It causes that it is impossible to connect to http-interface with clients which do not supports https (even if http port is provided by application server), i.e. following ModelControllerClient is not able to connect to http-interface when both http and https socket-binding is configured: {code} ModelControllerClient client = ModelControllerClient.Factory .create(new ModelControllerClientConfiguration.Builder() .setProtocol("remote+http") .setPort(9990) .setHostName("localhost") .setConnectionTimeout(10000).build()) {code} See: {code} curl -v -H 'Upgrade: jboss-remoting' http://localhost:9990 * Rebuilt URL to: http://localhost:9990/ * Hostname was NOT found in DNS cache * Trying 127.0.0.1... * Connected to localhost (127.0.0.1) port 9990 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.38.0 > Host: localhost:9990 > Accept: */* > Upgrade: jboss-remoting > < HTTP/1.1 302 Found < Connection: keep-alive < Location: https://localhost:9993/ < Content-Length: 0 < Date: Thu, 13 Apr 2017 11:59:56 GMT < * Connection #0 to host localhost left intact {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8578) Additional privileged blocks for JAXWS client running with Security Manager enabled

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-8578: ----------------------------------- Summary: Additional privileged blocks for JAXWS client running with Security Manager enabled Key: WFLY-8578 URL: https://issues.jboss.org/browse/WFLY-8578 Project: WildFly Issue Type: Bug Components: Web Services Reporter: Ivo Studensky Assignee: Ivo Studensky This is a follow up of CXF-5142 which should enable the JAXWS client to run with Security Manager enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8577) Additional privileged blocks for JAXWS client running with Security Manager enabled

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-8577: ----------------------------------- Summary: Additional privileged blocks for JAXWS client running with Security Manager enabled Key: WFLY-8577 URL: https://issues.jboss.org/browse/WFLY-8577 Project: WildFly Issue Type: Bug Components: Web Services Reporter: Ivo Studensky Assignee: Ivo Studensky This is a follow up of CXF-5142 which should enable the JAXWS client to run with Security Manager enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1523) Expired events don't allow a rule belonging to an inactive group to fire even when the group regain focus

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1523?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1523: ----------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > Expired events don't allow a rule belonging to an inactive group to fire even when the group regain focus > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1523 > URL: https://issues.jboss.org/browse/DROOLS-1523 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1523) Expired events don't allow a rule belonging to an inactive group to fire even when the group regain focus

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1523: ----------------------------------- Summary: Expired events don't allow a rule belonging to an inactive group to fire even when the group regain focus Key: DROOLS-1523 URL: https://issues.jboss.org/browse/DROOLS-1523 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Edson Tirelli -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1523) Expired events don't allow a rule belonging to an inactive group to fire even when the group regain focus

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1523?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1523: -------------------------------- Component/s: core engine > Expired events don't allow a rule belonging to an inactive group to fire even when the group regain focus > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1523 > URL: https://issues.jboss.org/browse/DROOLS-1523 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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