[JBoss JIRA] (WFCORE-3604) Attribute required-attributes of Elytron x500-attribute-principal-decoder cannot be added to configuration
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3604?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-3604:
---------------------------------
Affects Version/s: 4.0.0.Alpha10
> Attribute required-attributes of Elytron x500-attribute-principal-decoder cannot be added to configuration
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3604
> URL: https://issues.jboss.org/browse/WFCORE-3604
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 4.0.0.Alpha10
> Reporter: Ondrej Lukas
>
> When attribute {{required-attributes}} of Elytron x500-attribute-principal-decoder is added in CLI command then it fails with UnsupportedOperationException:
> {code}
> /subsystem=elytron/x500-attribute-principal-decoder=x500-decoder:add(attribute-name=cn,required-attributes=[cn])
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.UnsupportedOperationException",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3604) Attribute required-attributes of Elytron x500-attribute-principal-decoder cannot be added to configuration
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFCORE-3604:
------------------------------------
Summary: Attribute required-attributes of Elytron x500-attribute-principal-decoder cannot be added to configuration
Key: WFCORE-3604
URL: https://issues.jboss.org/browse/WFCORE-3604
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
When attribute {{required-attributes}} of Elytron x500-attribute-principal-decoder is added in CLI command then it fails with UnsupportedOperationException:
{code}
/subsystem=elytron/x500-attribute-principal-decoder=x500-decoder:add(attribute-name=cn,required-attributes=[cn])
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.UnsupportedOperationException",
"rolled-back" => true
}
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9788) EJB over HTTP fails with Arrays in Request
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-9788?page=com.atlassian.jira.plugin.... ]
jaikiran pai commented on WFLY-9788:
------------------------------------
I have pushed a branch to my personal repo which contains a test case to try and reproduce this. You can checkout the repo here https://github.com/jaikiran/wildfly/tree/wfly-9788 and follows these steps to build and test it.
// after the repo is cloned locally
git checkout wfly-9788
mvn clean install -DskipTests=true
cd testsuite/integration/basic
mvn clean test -Dtest=HttpRemoteEJBJndiBasedInvocationTestCase
There are 2 test methods you can focus on (one stateless bean, one stateful bean) in {{org.jboss.as.test.integration.ejb.remote.jndi.HttpRemoteEJBJndiBasedInvocationTestCase}} - {{testRemoteSFSBInvocation}} and {{testRemoteSLSBInvocation}}. Please try and get these failing by changing them in whichever way you think reproduces this issue.
Note that the branch that I have pointed you to use the 1.0.10-Final-SNAPSHOT of the EJB HTTP client library[1]. Please first build the PR that I have open to make sure this snapshot on your local system has those fixes, when you try and reproduce it.
[1] https://github.com/jaikiran/wildfly/commit/6361c8872c2ac17b717f64252fc45e...
> EJB over HTTP fails with Arrays in Request
> ------------------------------------------
>
> Key: WFLY-9788
> URL: https://issues.jboss.org/browse/WFLY-9788
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Heiko Lettmann
> Attachments: Test.zip
>
>
> I stumbled over the issue WFLY-9573. Then I updated to wildfly-http-client-1.0.9.Final which made a few invocations work. There I discovered another issue. I attached a modified Quickstart version to demonstrate it!
> Exception is on the client side:
> Exception in thread "main" javax.ejb.EJBException: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:128)
> at org.wildfly.httpclient.ejb.HttpInvocationHandler.lambda$handleInternal$0(HttpInvocationHandler.java:130)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:204)
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:126)
> ... 4 more
> Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:178)
> ... 5 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-2591) deployment add/add-content alternatives and required issues
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2591?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-2591:
----------------------------------
Fix Version/s: 4.0.0.Alpha3
> deployment add/add-content alternatives and required issues
> -----------------------------------------------------------
>
> Key: WFCORE-2591
> URL: https://issues.jboss.org/browse/WFCORE-2591
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Jean-Francois Denise
> Assignee: ehsavoie Hugonnet
> Priority: Minor
> Fix For: 4.0.0.Alpha3
>
>
> add operation
> - content should be required.
> - alternatives hash/bytes/url/path/input-stream-index/empty should be required.
> add-content operation
> - content should be required.
> - alternatives input-stream-index/hash/bytes/url should be required.
> - alternatives empty/relative-to/path should not be present in alternatives list.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3255) Complex type AttributeDefinition variants don't handle ParameterCorrector properly
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3255?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-3255:
----------------------------------
Fix Version/s: 4.0.0.Beta1
> Complex type AttributeDefinition variants don't handle ParameterCorrector properly
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-3255
> URL: https://issues.jboss.org/browse/WFCORE-3255
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.1.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 4.0.0.Beta1
>
>
> If a field in a complex attribute (i.e. one that uses Object...AttributeDefinition) has a ParameterCorrector configured, that corrector never gets called. That's because only a corrector on the top level attribute gets called.
> These classes should automatically use an internal corrector that first calls any corrector configured for fields, and then, if one is present, calls any top level corrector.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months