April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3200) Support Jackson 2 out of the box

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3200?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-3200: ------------------------------ Description: Wildfly can be configured to allow access to the native Jackson API. In order to accomplish this, you have to add a jboss-deployment-structure.xml that contains the following: {code:xml} <jboss-deployment-structure> <deployment> <exclusions> <module name="org.jboss.resteasy.resteasy-jackson-provider"/> </exclusions> <dependencies> <module name="org.jboss.resteasy.resteasy-jackson2-provider" services="import"/> </dependencies> </deployment> </jboss-deployment-structure> {code} It would be better if Jackson 2 were the default provider and this were not necessary. was: Wildfly can be configured to allow access to the native Jackson API. In order to accomplish this, you have to add a jboss-deployment-structure.xml that contains the following: <jboss-deployment-structure> <deployment> <exclusions> <module name="org.jboss.resteasy.resteasy-jackson-provider"/> </exclusions> <dependencies> <module name="org.jboss.resteasy.resteasy-jackson2-provider" services="import"/> </dependencies> </deployment> </jboss-deployment-structure> It would be better if Jackson 2 were the default provider and this were not necessary. > Support Jackson 2 out of the box > -------------------------------- > > Key: WFLY-3200 > URL: https://issues.jboss.org/browse/WFLY-3200 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 8.0.0.Final > Reporter: Nathaniel A. Johnson > Assignee: Stuart Douglas > Priority: Minor > > Wildfly can be configured to allow access to the native Jackson API. In order to accomplish this, you have to add a jboss-deployment-structure.xml that contains the following: > {code:xml} > <jboss-deployment-structure> > <deployment> > <exclusions> > <module name="org.jboss.resteasy.resteasy-jackson-provider"/> > </exclusions> > <dependencies> > <module name="org.jboss.resteasy.resteasy-jackson2-provider" services="import"/> > </dependencies> > </deployment> > </jboss-deployment-structure> > {code} > It would be better if Jackson 2 were the default provider and this were not necessary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3193) upgrade Generic JMS RA to 1.0.4.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3193?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3193: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1082617|https://bugzilla.redhat.com/show_bug.cgi?id=1082617] from POST to MODIFIED > upgrade Generic JMS RA to 1.0.4.Final > ------------------------------------- > > Key: WFLY-3193 > URL: https://issues.jboss.org/browse/WFLY-3193 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA, JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-815) NegotiationAuthenticator loses post data

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-815?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-815: -------------------------------------- Fix Version/s: Negotiation_2_3_0_Final > NegotiationAuthenticator loses post data > ---------------------------------------- > > Key: SECURITY-815 > URL: https://issues.jboss.org/browse/SECURITY-815 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_0_Final > > > The NegotiationAuthenticator loses post data. > A customer is attempting to use Negotiation along with PicketLink at the IDP. This works fine as long as the SP is using HTTP-Redirect SAML binding. > If the SP is using HTTP-Redirect, then this issue is avoided as the SAMLRequest is passed along through the redirects on the URL. > If the HTTP-POST binding is used, then the NegotiationAuthenticator will lose the SAMLRequest post parameter. This means that after a user is successfully authenticated, the IDP will not know where to redirect the user to. As a result, the user will be left at the IDP index.html page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-815) NegotiationAuthenticator loses post data

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-815?page=com.atlassian.jira.plug... ] Derek Horton updated SECURITY-815: ---------------------------------- Git Pull Request: https://github.com/wildfly/jboss-negotiation/pull/3 > NegotiationAuthenticator loses post data > ---------------------------------------- > > Key: SECURITY-815 > URL: https://issues.jboss.org/browse/SECURITY-815 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Darran Lofthouse > > The NegotiationAuthenticator loses post data. > A customer is attempting to use Negotiation along with PicketLink at the IDP. This works fine as long as the SP is using HTTP-Redirect SAML binding. > If the SP is using HTTP-Redirect, then this issue is avoided as the SAMLRequest is passed along through the redirects on the URL. > If the HTTP-POST binding is used, then the NegotiationAuthenticator will lose the SAMLRequest post parameter. This means that after a user is successfully authenticated, the IDP will not know where to redirect the user to. As a result, the user will be left at the IDP index.html page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-815) NegotiationAuthenticator loses post data

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-815?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-815: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1030053 > NegotiationAuthenticator loses post data > ---------------------------------------- > > Key: SECURITY-815 > URL: https://issues.jboss.org/browse/SECURITY-815 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Derek Horton > Assignee: Darran Lofthouse > > The NegotiationAuthenticator loses post data. > A customer is attempting to use Negotiation along with PicketLink at the IDP. This works fine as long as the SP is using HTTP-Redirect SAML binding. > If the SP is using HTTP-Redirect, then this issue is avoided as the SAMLRequest is passed along through the redirects on the URL. > If the HTTP-POST binding is used, then the NegotiationAuthenticator will lose the SAMLRequest post parameter. This means that after a user is successfully authenticated, the IDP will not know where to redirect the user to. As a result, the user will be left at the IDP index.html page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-815) NegotiationAuthenticator loses post data

by Derek Horton (JIRA)

Derek Horton created SECURITY-815: ------------------------------------- Summary: NegotiationAuthenticator loses post data Key: SECURITY-815 URL: https://issues.jboss.org/browse/SECURITY-815 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2_2_5 Reporter: Derek Horton Assignee: Darran Lofthouse The NegotiationAuthenticator loses post data. A customer is attempting to use Negotiation along with PicketLink at the IDP. This works fine as long as the SP is using HTTP-Redirect SAML binding. If the SP is using HTTP-Redirect, then this issue is avoided as the SAMLRequest is passed along through the redirects on the URL. If the HTTP-POST binding is used, then the NegotiationAuthenticator will lose the SAMLRequest post parameter. This means that after a user is successfully authenticated, the IDP will not know where to redirect the user to. As a result, the user will be left at the IDP index.html page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3199) Remove external BOM from jboss-as-parent

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/WFLY-3199?page=com.atlassian.jira.plugin.... ] Paul Gier updated WFLY-3199: ---------------------------- Priority: Minor (was: Major) > Remove external BOM from jboss-as-parent > ---------------------------------------- > > Key: WFLY-3199 > URL: https://issues.jboss.org/browse/WFLY-3199 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Priority: Minor > Fix For: 8.0.1.Final > > > The jboss-as-parent pom currently depends on an external BOM (apacheds-parent) to get some dependency versions. This means that it's not obvious which version is used for some dependencies. And it's possible that a version could be unintentionally upgraded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3199) Remove external BOM from jboss-as-parent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3199?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3199: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1082820 > Remove external BOM from jboss-as-parent > ---------------------------------------- > > Key: WFLY-3199 > URL: https://issues.jboss.org/browse/WFLY-3199 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 8.0.1.Final > > > The jboss-as-parent pom currently depends on an external BOM (apacheds-parent) to get some dependency versions. This means that it's not obvious which version is used for some dependencies. And it's possible that a version could be unintentionally upgraded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3199) Remove external BOM from jboss-as-parent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3199?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3199: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1082820|https://bugzilla.redhat.com/show_bug.cgi?id=1082820] from NEW to POST > Remove external BOM from jboss-as-parent > ---------------------------------------- > > Key: WFLY-3199 > URL: https://issues.jboss.org/browse/WFLY-3199 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 8.0.1.Final > > > The jboss-as-parent pom currently depends on an external BOM (apacheds-parent) to get some dependency versions. This means that it's not obvious which version is used for some dependencies. And it's possible that a version could be unintentionally upgraded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-814) Correct the JBoss Negotiation project hierarchy

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-814: ----------------------------------------- Summary: Correct the JBoss Negotiation project hierarchy Key: SECURITY-814 URL: https://issues.jboss.org/browse/SECURITY-814 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: Negotiation_2_3_0_CR1 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_3_0_Final The build outputs the following: - {code} [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.security:jboss-negotiation-project:pom:2.3.0.Final-SNAPSHOT [WARNING] 'parent.relativePath' points at org.jboss.security:jboss-negotiation-main instead of org.jboss:jboss-parent, please verify your project structure @ line 3, column 11 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.security:jboss-negotiation-common:jar:2.3.0.Final-SNAPSHOT [WARNING] 'parent.relativePath' of POM org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT (/home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml) points at org.jboss.security:jboss-negotiation-main instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT, /home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml, line 3, column 11 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.security:jboss-negotiation-extras:jar:2.3.0.Final-SNAPSHOT [WARNING] 'parent.relativePath' of POM org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT (/home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml) points at org.jboss.security:jboss-negotiation-main instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT, /home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml, line 3, column 11 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.security:jboss-negotiation-net:jar:2.3.0.Final-SNAPSHOT [WARNING] 'parent.relativePath' of POM org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT (/home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml) points at org.jboss.security:jboss-negotiation-main instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT, /home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml, line 3, column 11 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.security:jboss-negotiation-ntlm:jar:2.3.0.Final-SNAPSHOT [WARNING] 'parent.relativePath' of POM org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT (/home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml) points at org.jboss.security:jboss-negotiation-main instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT, /home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml, line 3, column 11 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.security:jboss-negotiation-spnego:jar:2.3.0.Final-SNAPSHOT [WARNING] 'parent.relativePath' of POM org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT (/home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml) points at org.jboss.security:jboss-negotiation-main instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT, /home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml, line 3, column 11 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.security:jboss-negotiation-toolkit:war:2.3.0.Final-SNAPSHOT [WARNING] 'parent.relativePath' of POM org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT (/home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml) points at org.jboss.security:jboss-negotiation-main instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT, /home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml, line 3, column 11 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.security:jboss-negotiation-main:pom:2.3.0.Final-SNAPSHOT [WARNING] 'parent.relativePath' of POM org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT (/home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml) points at org.jboss.security:jboss-negotiation-main instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss.security:jboss-negotiation-project:2.3.0.Final-SNAPSHOT, /home/darranl/src/wildfly/jboss-negotiation/parent/pom.xml, line 3, column 11 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2014