January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2220) Upgrade to WildFly Elytron 1.1.0.Beta20

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2220: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta20 Key: WFCORE-2220 URL: https://issues.jboss.org/browse/WFCORE-2220 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha20 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-888) Release WildFly Elytron 1.1.0.Beta20

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-888: ------------------------------------ Summary: Release WildFly Elytron 1.1.0.Beta20 Key: ELY-888 URL: https://issues.jboss.org/browse/ELY-888 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta20 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-884) Add a SortedMechanismFactory for HTTP mechansisms

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-884?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-884. ---------------------------------- Resolution: Done > Add a SortedMechanismFactory for HTTP mechansisms > ------------------------------------------------- > > Key: ELY-884 > URL: https://issues.jboss.org/browse/ELY-884 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta20 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-877) Allow GSSCredentialCredential to contain 'additional credentials;

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-877?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-877. ---------------------------------- Resolution: Done > Allow GSSCredentialCredential to contain 'additional credentials; > ----------------------------------------------------------------- > > Key: ELY-877 > URL: https://issues.jboss.org/browse/ELY-877 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credentials > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta20 > > > Additional intermediate credentials are created when creating the GSSCredential - these should be made available from the GSSCredentialFactory if required so they can be used elsewhere. > i.e. Parsing SPNEGO messages to make credential delegation possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-883) Rename GSSCredentialCredential to GSSKerberosCredential

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-883?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-883. ---------------------------------- Resolution: Done > Rename GSSCredentialCredential to GSSKerberosCredential > ------------------------------------------------------- > > Key: ELY-883 > URL: https://issues.jboss.org/browse/ELY-883 > Project: WildFly Elytron > Issue Type: Task > Components: Credentials > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta20 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-875) The SpnegoAuthenticationMechanism is not setting the delegated credential.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-875?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-875. ---------------------------------- Resolution: Done > The SpnegoAuthenticationMechanism is not setting the delegated credential. > -------------------------------------------------------------------------- > > Key: ELY-875 > URL: https://issues.jboss.org/browse/ELY-875 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta20 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-879) HTTP Digest mechanism not checking length of username causing IllegalArgument Exception

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-879?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-879. ---------------------------------- Resolution: Done > HTTP Digest mechanism not checking length of username causing IllegalArgument Exception > --------------------------------------------------------------------------------------- > > Key: ELY-879 > URL: https://issues.jboss.org/browse/ELY-879 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta20 > > > In case when empty username is passed during authentication to Management Console then exception is thrown to server log and Internal Server Error (status 500) is returned to user (which leads to displaying "Connect to Management Interface" page. User is not able to try to login again. > In WildFly 10.1.0 this scenario works fine - after passing empty username during authentication, authentication failed and login window is displayed again. I request blocker due to regression. > Exception thrown to server log: > {code} > ERROR [io.undertow.request] (management task-3) UT005071: Undertow request failed HttpServerExchange{ GET /management request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[en-US,en;q=0.5], Accept-Encoding=[gzip, deflate], User-Agent=[Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0], Connection=[keep-alive], Authorization=[Digest username="", realm="ManagementRealm", nonce="AAAAAwAAAlzTPVPLC0qPi6CaEhTCHZa+QjsuAjn3OsQXcuDYAxrOtc+rRMs=", uri="/management", algorithm=MD5, response="cbd764e6c09577625476340f7bcfc84d", opaque="00000000000000000000000000000000"], Content-Type=[text/plain; charset=utf-8], Cookie=[__utma=111872281.1874867570.1477040206.1479886566.1479982414.11; __utmz=111872281.1477040206.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmb=111872281.5.10.1479982414; __utmt=1; __utmc=111872281], Referer=[http://localhost:9990/console/App.html], Host=[localhost:9990]} response {X-Frame-Options=[SAMEORIGIN]}}: java.lang.IllegalArgumentException > at javax.security.auth.callback.NameCallback.<init>(NameCallback.java:90) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.getH_A1(DigestAuthenticationMechanism.java:233) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.validateResponse(DigestAuthenticationMechanism.java:189) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.evaluateRequest(DigestAuthenticationMechanism.java:121) > at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:115) > at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:106) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:90) > at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:74) > at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:82) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:50) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:207) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3583) Convert mod_cluster excluded context into an xs:list of host:context

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3583?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-3583: --------------------------------- Priority: Minor (was: Major) > Convert mod_cluster excluded context into an xs:list of host:context > -------------------------------------------------------------------- > > Key: WFLY-3583 > URL: https://issues.jboss.org/browse/WFLY-3583 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 8.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > {noformat} > // TODO: Convert into an xs:list of host:context > static final SimpleAttributeDefinition EXCLUDED_CONTEXTS = SimpleAttributeDefinitionBuilder.create(CommonAttributes.EXCLUDED_CONTEXTS, ModelType.STRING, true) > .setAllowExpression(true) > .setDefaultValue(new ModelNode("ROOT,invoker,jbossws,juddi,console")) > .setRestartAllServices() > .build(); > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1416) DRL Dumper Not Printing the content of ConditionalBranch

by Siyad Theyparambil Mohammed (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1416?page=com.atlassian.jira.plugi... ] Siyad Theyparambil Mohammed commented on DROOLS-1416: ----------------------------------------------------- HI [~mfusco] Which version of Jar should we download inorder to get this fix ? > DRL Dumper Not Printing the content of ConditionalBranch > -------------------------------------------------------- > > Key: DROOLS-1416 > URL: https://issues.jboss.org/browse/DROOLS-1416 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 6.4.0.Final > Reporter: Siyad Theyparambil Mohammed > Assignee: Mario Fusco > Fix For: 7.0.0.CR1 > > > While trying to use conditionalbranch api for handling multiple if-then blocks, the DRL dumper is not printing the content we have used for conditionalbranch. Please find the sample code below and the restuls > *+Code+* > PackageDescr pkg = DescrFactory.newPackage() > .name( "org.drools.compiler" ) > .newRule().name( "test" ) > .lhs() > .pattern("Cheese").constraint( "type == \"stilton\"" ).end() > .conditionalBranch() > .condition().constraint("price < 10").end() > .consequence().name("c1").end() > .end() > .pattern("Cheese").constraint( "type == \"cheddar\"" ).end() > .conditionalBranch() > .condition().constraint("price > 10").end() > .consequence().name("c2").end() > .end() > .end() > .rhs( "// do something" ) > .namedRhs( "c1", "// do something else\n" ) > .end() > .getDescr(); > > return new DrlDumper().dump( pkg ); > *+Output+* > package org.drools.compiler > rule "test" > when > Cheese( type == "stilton" ) > > Cheese( type == "cheddar" ) > > then > // do something > then[c1] > // do something else > end > In the above example the content "price < 10" and "price > 10" which we have used for conditionalBranch is not getting printed. On further investigation we found the drl.mvel template does not have the import org.drools.compiler.lang.descr.ConditionalBranchDescr. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2219) Ability to turn off boot time capability resolution leniency in admin-only mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2219?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2219: ------------------------------------- Description: Currently boot is lenient about broken capability requirements during admin-only boot. We need a way to turn this off. The current behavior is a fine default, as it allows users to boot a broken config in --admin-only and then fix the config. Without this the user is forced to rely on xml editing. But there are other use cases for admin-only, for example in automated provisioning systems or testing systems, where the user can quite reasonable want a broken config to immediately generate a boot failure, as the automated system is not designed to handle incorrect initial input. was: Currently boot is lenient about broken capability requirements during admin-only boot. We need a way to turn this off. The current behavior is a fine default, as it allows users to boot a broken config in --admin-only and then fix the config. Without this the user is forced to rely on xml editing. But there are other use cases for admin-only, for example in automated provisioning systems or testing systems, where the user can quite reasonable want a broken config immediately generate an boot failure, as the automated system is not designed to handle incorrect initial input. > Ability to turn off boot time capability resolution leniency in admin-only mode > ------------------------------------------------------------------------------- > > Key: WFCORE-2219 > URL: https://issues.jboss.org/browse/WFCORE-2219 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > > Currently boot is lenient about broken capability requirements during admin-only boot. We need a way to turn this off. > The current behavior is a fine default, as it allows users to boot a broken config in --admin-only and then fix the config. Without this the user is forced to rely on xml editing. > But there are other use cases for admin-only, for example in automated provisioning systems or testing systems, where the user can quite reasonable want a broken config to immediately generate a boot failure, as the automated system is not designed to handle incorrect initial input. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 January 2017