[JBoss JIRA] (WFLY-8070) Messaging subsystem passwords and credential-reference should be mutually exclusive
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-8070?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFLY-8070:
-------------------------------
Labels: user_experience (was: )
> Messaging subsystem passwords and credential-reference should be mutually exclusive
> -----------------------------------------------------------------------------------
>
> Key: WFLY-8070
> URL: https://issues.jboss.org/browse/WFLY-8070
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Labels: user_experience
>
> I don't see any useful use case when I want to configure password attribute in conjuction with credential-reference.
> Please mark password attribute and credential-reference in management model as "alternatives".
> alternatives – List of string – Indicates an exclusive relationship between attributes. If this attribute is defined, the other attributes listed in this descriptor's value should be undefined (even if their required descriptor says true; i.e. the presence of this attribute satisfies the requirement.) Default is undefined; i.e. this does not apply to most attributes.
> It applies to:
> * {bridge}
> ** Attributes {{password}} and {{credential-reference}} should be mutually exclusive.
> * {jms-bridge}
> ** Attributes {{source-password}} and {{source-credential-reference}} should be mutually exclusive.
> ** Attributes {{target-password}} and {{target-credential-reference}} should be mutually exclusive.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8070) Messaging subsystem passwords and credential-reference should be mutually exclusive
by Martin Choma (JIRA)
Martin Choma created WFLY-8070:
----------------------------------
Summary: Messaging subsystem passwords and credential-reference should be mutually exclusive
Key: WFLY-8070
URL: https://issues.jboss.org/browse/WFLY-8070
Project: WildFly
Issue Type: Bug
Components: JMS, Security
Reporter: Martin Choma
Assignee: Jeff Mesnil
I don't see any useful use case when I want to configure password attribute in conjuction with credential-reference.
Please mark password attribute and credential-reference in management model as "alternatives".
alternatives – List of string – Indicates an exclusive relationship between attributes. If this attribute is defined, the other attributes listed in this descriptor's value should be undefined (even if their required descriptor says true; i.e. the presence of this attribute satisfies the requirement.) Default is undefined; i.e. this does not apply to most attributes.
It applies to:
* {bridge}
** Attributes {{password}} and {{credential-reference}} should be mutually exclusive.
* {jms-bridge}
** Attributes {{source-password}} and {{source-credential-reference}} should be mutually exclusive.
** Attributes {{target-password}} and {{target-credential-reference}} should be mutually exclusive.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1369) Property reactive triggers stateful working memory corruption on CoachShuttleGathering
by Jiri Locker (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1369?page=com.atlassian.jira.plugi... ]
Jiri Locker updated DROOLS-1369:
--------------------------------
Attachment: (was: DroolsReproducerTest.java)
> Property reactive triggers stateful working memory corruption on CoachShuttleGathering
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-1369
> URL: https://issues.jboss.org/browse/DROOLS-1369
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Attachments: DroolsReproducerTest.java
>
>
> Not confirmed yet that this is a drools bug, but it probably is :)
> Jiri is isolating.
> To reproduce:
> Use https://github.com/droolsjbpm/optaplanner/pull/234
> and run CloudShuttleGatheringPerformanceTest.
> {code}
> java.lang.IllegalStateException: Impossible VariableListener corruption: the expectedWorkingScore (0hard/-397050soft) is not the workingScore (-2000000000hard/-397050soft) after all VariableListeners were triggered without changes to the genuine variables.
> But all the shadow variable values are still the same, so this is impossible.
> at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertShadowVariablesAreNotStale(AbstractScoreDirector.java:488)
> at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertShadowVariablesAreNotStale(DefaultSolverScope.java:140)
> at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertShadowVariablesAreNotStale(AbstractPhaseScope.java:171)
> at org.optaplanner.core.impl.phase.AbstractPhase.predictWorkingStepScore(AbstractPhase.java:169)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.doStep(DefaultLocalSearchPhase.java:102)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:92)
> at org.optaplanner.core.impl.solver.AbstractSolver.runPhases(AbstractSolver.java:87)
> at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:160)
> at org.optaplanner.examples.common.app.SolverPerformanceTest.runSpeedTest(SolverPerformanceTest.java:65)
> at org.optaplanner.examples.coachshuttlegathering.app.CoachShuttleGatheringPerformanceTest.solveDemo01FastAssert(CoachShuttleGatheringPerformanceTest.java:52)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1369) Property reactive triggers stateful working memory corruption on CoachShuttleGathering
by Jiri Locker (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1369?page=com.atlassian.jira.plugi... ]
Jiri Locker updated DROOLS-1369:
--------------------------------
Attachment: DroolsReproducerTest.java
> Property reactive triggers stateful working memory corruption on CoachShuttleGathering
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-1369
> URL: https://issues.jboss.org/browse/DROOLS-1369
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Attachments: DroolsReproducerTest.java
>
>
> Not confirmed yet that this is a drools bug, but it probably is :)
> Jiri is isolating.
> To reproduce:
> Use https://github.com/droolsjbpm/optaplanner/pull/234
> and run CloudShuttleGatheringPerformanceTest.
> {code}
> java.lang.IllegalStateException: Impossible VariableListener corruption: the expectedWorkingScore (0hard/-397050soft) is not the workingScore (-2000000000hard/-397050soft) after all VariableListeners were triggered without changes to the genuine variables.
> But all the shadow variable values are still the same, so this is impossible.
> at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertShadowVariablesAreNotStale(AbstractScoreDirector.java:488)
> at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertShadowVariablesAreNotStale(DefaultSolverScope.java:140)
> at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertShadowVariablesAreNotStale(AbstractPhaseScope.java:171)
> at org.optaplanner.core.impl.phase.AbstractPhase.predictWorkingStepScore(AbstractPhase.java:169)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.doStep(DefaultLocalSearchPhase.java:102)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:92)
> at org.optaplanner.core.impl.solver.AbstractSolver.runPhases(AbstractSolver.java:87)
> at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:160)
> at org.optaplanner.examples.common.app.SolverPerformanceTest.runSpeedTest(SolverPerformanceTest.java:65)
> at org.optaplanner.examples.coachshuttlegathering.app.CoachShuttleGatheringPerformanceTest.solveDemo01FastAssert(CoachShuttleGatheringPerformanceTest.java:52)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1433) DMN Model node with no typeRef affected by wrong validation message
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-1433:
--------------------------------------
Summary: DMN Model node with no typeRef affected by wrong validation message
Key: DROOLS-1433
URL: https://issues.jboss.org/browse/DROOLS-1433
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
In the following example:
{code:xml}
<decision id="d_BureauCallType" name="BureauCallType">
<variable name="BureauCallType" typeRef="tns:tBureauCallType"/>
<informationRequirement>
<requiredDecision href="#d_Pre-bureauRiskCategory"/>
</informationRequirement>
<knowledgeRequirement>
<requiredKnowledge href="#b_BureauCallTypeTable"/>
</knowledgeRequirement>
<invocation>
<literalExpression>
<text>BureauCallTypeTable</text>
</literalExpression>
<binding>
<parameter id="_65deeb90-626c-4cce-9485-eae9455b2194" name="Pre-bureauRiskCategory"/>
<literalExpression>
<text>Pre-bureauRiskCategory</text>
</literalExpression>
</binding>
</invocation>
</decision>
{code}
the {{invocation}} and {{literalExpression}} node are receiving a wrong validation message for "This element indicates a 'typeRef' which is not in FEEL namespace and not defined with itemDefinition", despite they don't provide any {{typeRef}} at all.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1369) Property reactive triggers stateful working memory corruption on CoachShuttleGathering
by Jiri Locker (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1369?page=com.atlassian.jira.plugi... ]
Jiri Locker commented on DROOLS-1369:
-------------------------------------
Reproducer attached. Source with history can be viewed at https://github.com/yurloc/drools-reproducer/blob/drools1369/src/test/java....
> Property reactive triggers stateful working memory corruption on CoachShuttleGathering
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-1369
> URL: https://issues.jboss.org/browse/DROOLS-1369
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Attachments: DroolsReproducerTest.java
>
>
> Not confirmed yet that this is a drools bug, but it probably is :)
> Jiri is isolating.
> To reproduce:
> Use https://github.com/droolsjbpm/optaplanner/pull/234
> and run CloudShuttleGatheringPerformanceTest.
> {code}
> java.lang.IllegalStateException: Impossible VariableListener corruption: the expectedWorkingScore (0hard/-397050soft) is not the workingScore (-2000000000hard/-397050soft) after all VariableListeners were triggered without changes to the genuine variables.
> But all the shadow variable values are still the same, so this is impossible.
> at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertShadowVariablesAreNotStale(AbstractScoreDirector.java:488)
> at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertShadowVariablesAreNotStale(DefaultSolverScope.java:140)
> at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertShadowVariablesAreNotStale(AbstractPhaseScope.java:171)
> at org.optaplanner.core.impl.phase.AbstractPhase.predictWorkingStepScore(AbstractPhase.java:169)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.doStep(DefaultLocalSearchPhase.java:102)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:92)
> at org.optaplanner.core.impl.solver.AbstractSolver.runPhases(AbstractSolver.java:87)
> at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:160)
> at org.optaplanner.examples.common.app.SolverPerformanceTest.runSpeedTest(SolverPerformanceTest.java:65)
> at org.optaplanner.examples.coachshuttlegathering.app.CoachShuttleGatheringPerformanceTest.solveDemo01FastAssert(CoachShuttleGatheringPerformanceTest.java:52)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1369) Property reactive triggers stateful working memory corruption on CoachShuttleGathering
by Jiri Locker (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1369?page=com.atlassian.jira.plugi... ]
Jiri Locker updated DROOLS-1369:
--------------------------------
Attachment: DroolsReproducerTest.java
> Property reactive triggers stateful working memory corruption on CoachShuttleGathering
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-1369
> URL: https://issues.jboss.org/browse/DROOLS-1369
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Attachments: DroolsReproducerTest.java
>
>
> Not confirmed yet that this is a drools bug, but it probably is :)
> Jiri is isolating.
> To reproduce:
> Use https://github.com/droolsjbpm/optaplanner/pull/234
> and run CloudShuttleGatheringPerformanceTest.
> {code}
> java.lang.IllegalStateException: Impossible VariableListener corruption: the expectedWorkingScore (0hard/-397050soft) is not the workingScore (-2000000000hard/-397050soft) after all VariableListeners were triggered without changes to the genuine variables.
> But all the shadow variable values are still the same, so this is impossible.
> at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertShadowVariablesAreNotStale(AbstractScoreDirector.java:488)
> at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertShadowVariablesAreNotStale(DefaultSolverScope.java:140)
> at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertShadowVariablesAreNotStale(AbstractPhaseScope.java:171)
> at org.optaplanner.core.impl.phase.AbstractPhase.predictWorkingStepScore(AbstractPhase.java:169)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.doStep(DefaultLocalSearchPhase.java:102)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:92)
> at org.optaplanner.core.impl.solver.AbstractSolver.runPhases(AbstractSolver.java:87)
> at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:160)
> at org.optaplanner.examples.common.app.SolverPerformanceTest.runSpeedTest(SolverPerformanceTest.java:65)
> at org.optaplanner.examples.coachshuttlegathering.app.CoachShuttleGatheringPerformanceTest.solveDemo01FastAssert(CoachShuttleGatheringPerformanceTest.java:52)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-972) Provide a way to correlate HTTP management requests
by Harald Pehl (JIRA)
[ https://issues.jboss.org/browse/WFCORE-972?page=com.atlassian.jira.plugin... ]
Harald Pehl commented on WFCORE-972:
------------------------------------
That's right, the main driver is to support multiple independent management requests in parallel. The main use case is when we execute r-r-d operations. For complex UIs like Infinispan or ActiveMQ we need to read dozens of resource descriptions upfront.
Right now we partition these r-r-d operations into composite operations with a max of three operations per composite (to reduce the payload). Then we execute and parse the composite operations one after the other. That's necessary to unambiguously map the operation to the result. If we had an unique identifier (correlation id) on the request / response, we would be able to send the operations in parallel and use the correlation id for the mapping.
> Provide a way to correlate HTTP management requests
> ---------------------------------------------------
>
> Key: WFCORE-972
> URL: https://issues.jboss.org/browse/WFCORE-972
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 3.0.0.Beta1
>
>
> {noformat}
> public class CorrelationHandler implements HttpHandler {
> private static final HttpString HEADER = new HttpString("X-CORR-ID");
> private final HttpHandler next;
> public CorrelationHandler(HttpHandler next) {
> this.next = next;
> }
> @Override
> public void handleRequest(HttpServerExchange exchange) throws Exception {
> String corr = exchange.getRequestHeaders().getFirst(HEADER);
> if(corr != null) {
> exchange.getResponseHeaders().put(HEADER, corr);
> }
> next.handleRequest(exchange);
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-972) Provide a way to correlate HTTP management requests
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/WFCORE-972?page=com.atlassian.jira.plugin... ]
Heiko Braun commented on WFCORE-972:
------------------------------------
I think X-Correlation-ID is fine as well. The rationale behind this request was to support parallel management request execution from the HAL console. [~harald.pehl] Do you want comment on this?
> Provide a way to correlate HTTP management requests
> ---------------------------------------------------
>
> Key: WFCORE-972
> URL: https://issues.jboss.org/browse/WFCORE-972
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 3.0.0.Beta1
>
>
> {noformat}
> public class CorrelationHandler implements HttpHandler {
> private static final HttpString HEADER = new HttpString("X-CORR-ID");
> private final HttpHandler next;
> public CorrelationHandler(HttpHandler next) {
> this.next = next;
> }
> @Override
> public void handleRequest(HttpServerExchange exchange) throws Exception {
> String corr = exchange.getRequestHeaders().getFirst(HEADER);
> if(corr != null) {
> exchange.getResponseHeaders().put(HEADER, corr);
> }
> next.handleRequest(exchange);
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (ELY-940) key-store-ssl-certificate -> key-store-clear-password is wrapping parsing inside the Supplier
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-940:
------------------------------------
Summary: key-store-ssl-certificate -> key-store-clear-password is wrapping parsing inside the Supplier
Key: ELY-940
URL: https://issues.jboss.org/browse/ELY-940
Project: WildFly Elytron
Issue Type: Task
Components: Authentication Client
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.1.0.Beta24
This means we get errors like this where the parser is accessed after parsing should have finished: -
{{[disconnected /] connect
java.lang.IllegalStateException: Current event not START_ELEMENT
at com.ctc.wstx.sr.BasicStreamReader.getAttributeCount(BasicStreamReader.java:584)
at org.wildfly.client.config.BasicXMLStreamReader.getAttributeCount(BasicXMLStreamReader.java:191)
at org.wildfly.client.config.AbstractDelegatingXMLStreamReader.getAttributeCount(AbstractDelegatingXMLStreamReader.java:148)
at org.wildfly.client.config.AbstractDelegatingXMLStreamReader.getAttributeCount(AbstractDelegatingXMLStreamReader.java:148)
at org.wildfly.security.auth.client.ElytronXmlParser.parseClearPassword(ElytronXmlParser.java:1864)
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$43(ElytronXmlParser.java:1270)
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$44(ElytronXmlParser.java:1286)
at org.wildfly.security.auth.client.ElytronXmlParser$PrivateKeyKeyStoreEntryCredentialFactory.get(ElytronXmlParser.java:2232)
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextType$5(ElytronXmlParser.java:434)
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseSslContextRuleType$6(ElytronXmlParser.java:457)
at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$8(ElytronXmlParser.java:493)
at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:292)
}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months