[JBoss JIRA] (WFCORE-2016) Change sasl-authentication-factor for management auth works after reload, but not after server restart
by Zach Rhoads (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2016?page=com.atlassian.jira.plugi... ]
Zach Rhoads updated WFCORE-2016:
--------------------------------
Description:
I can successfully configure a new sasl-authentication-factory and assign it to the management interface:
{code}
/subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir)
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add()
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:set-password(clear={password="password123"})
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add-attribute(name=Roles, value=["Admin","Guest"])
/subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles)
/subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper)
/subsystem=elytron/sasl-authentication-factory=example-sasl-auth:add(sasl-server-factory=configured,security-domain=exampleFsSD,mechanism-configurations=[{mechanism-name=DIGEST-MD5,mechanism-realm-configurations=[{realm-name=exampleSaslRealm}]}])
/core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=example-sasl-auth)
reload
{code}
after reload, i am forced to re-authenticate and it succeeds:
{code}
[standalone@localhost:9990 /] reload
Authenticating against security realm: exampleSaslRealm
Username: user1
Password:
[standalone@localhost:9990 /]
{code}
Once i restart the server though and try to connect, i get a timeout:
{code}
$ ./jboss-cli.sh -c
Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out
{code}
It also fails if i force no local auth:
{code}
$ ./jboss-cli.sh -c --no-local-auth
Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out
{code}/
was:
I can successfully configure a new sasl-authentication-factory and assign it to the management interface:
{code}
/subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir)
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add()
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:set-password(clear={password="password123"})
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add-attribute(name=Roles, value=["Admin","Guest"])
/subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles)
/subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper)
/subsystem=elytron/sasl-authentication-factory=example-sasl-auth:add(sasl-server-factory=configured,security-domain=exampleFsSD,mechanism-configurations=[{mechanism-name=DIGEST-MD5,mechanism-realm-configurations=[{realm-name=exampleSaslRealm}]}])
/core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=example-sasl-auth)
reload
{code}
after reload, i am forced to re-authenticate and it succeeds:
{code}
[standalone@localhost:9990 /] reload
Authenticating against security realm: exampleSaslRealm
Username: user1
Password:
[standalone@localhost:9990 /]
{code}
Once i restart the server though and try to connect, i get a timeout:
{code}
$ ./jboss-cli.sh -c
Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out
{code}
> Change sasl-authentication-factor for management auth works after reload, but not after server restart
> ------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2016
> URL: https://issues.jboss.org/browse/WFCORE-2016
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Zach Rhoads
> Assignee: Darran Lofthouse
>
> I can successfully configure a new sasl-authentication-factory and assign it to the management interface:
> {code}
> /subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir)
> /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add()
> /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:set-password(clear={password="password123"})
> /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add-attribute(name=Roles, value=["Admin","Guest"])
> /subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles)
> /subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper)
> /subsystem=elytron/sasl-authentication-factory=example-sasl-auth:add(sasl-server-factory=configured,security-domain=exampleFsSD,mechanism-configurations=[{mechanism-name=DIGEST-MD5,mechanism-realm-configurations=[{realm-name=exampleSaslRealm}]}])
> /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=example-sasl-auth)
> reload
> {code}
> after reload, i am forced to re-authenticate and it succeeds:
> {code}
> [standalone@localhost:9990 /] reload
> Authenticating against security realm: exampleSaslRealm
> Username: user1
> Password:
> [standalone@localhost:9990 /]
> {code}
> Once i restart the server though and try to connect, i get a timeout:
> {code}
> $ ./jboss-cli.sh -c
> Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out
> {code}
> It also fails if i force no local auth:
> {code}
> $ ./jboss-cli.sh -c --no-local-auth
> Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out
> {code}/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-2016) Change sasl-authentication-factor for management auth works after reload, but not after server restart
by Zach Rhoads (JIRA)
Zach Rhoads created WFCORE-2016:
-----------------------------------
Summary: Change sasl-authentication-factor for management auth works after reload, but not after server restart
Key: WFCORE-2016
URL: https://issues.jboss.org/browse/WFCORE-2016
Project: WildFly Core
Issue Type: Bug
Reporter: Zach Rhoads
Assignee: Darran Lofthouse
I can successfully configure a new sasl-authentication-factory and assign it to the management interface:
{code}
/subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir)
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add()
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:set-password(clear={password="password123"})
/subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add-attribute(name=Roles, value=["Admin","Guest"])
/subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles)
/subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper)
/subsystem=elytron/sasl-authentication-factory=example-sasl-auth:add(sasl-server-factory=configured,security-domain=exampleFsSD,mechanism-configurations=[{mechanism-name=DIGEST-MD5,mechanism-realm-configurations=[{realm-name=exampleSaslRealm}]}])
/core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=example-sasl-auth)
reload
{code}
after reload, i am forced to re-authenticate and it succeeds:
{code}
[standalone@localhost:9990 /] reload
Authenticating against security realm: exampleSaslRealm
Username: user1
Password:
[standalone@localhost:9990 /]
{code}
Once i restart the server though and try to connect, i get a timeout:
{code}
$ ./jboss-cli.sh -c
Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (DROOLS-785) no MVEL debugger registered to handle breakpoint
by Maurice Betzel (JIRA)
[ https://issues.jboss.org/browse/DROOLS-785?page=com.atlassian.jira.plugin... ]
Maurice Betzel commented on DROOLS-785:
---------------------------------------
...AND of course insert a breakpoint :)
> no MVEL debugger registered to handle breakpoint
> ------------------------------------------------
>
> Key: DROOLS-785
> URL: https://issues.jboss.org/browse/DROOLS-785
> Project: Drools
> Issue Type: Bug
> Components: core engine, eclipse plugin
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Environment: Win 7 64, JBoss Developer Studio Version: 8.1.0.GA, JBossAS Tools 3.0.3.Final-v20150325-0035-B129, Java 1.7.0_76
> Reporter: Maurice Betzel
> Assignee: Petr Široký
>
> Executing Drools-Examples 6.0.2.Final from github containing MVEL dialect resulted in runtime exception:
> 2015-05-16 14:35:28,603 [main] INFO Found kmodule: file:/C:/Users/x3.mbetzel/Development/workspaces/jboss-drools/drools-examples-62/target/classes/META-INF/kmodule.xml
> 2015-05-16 14:35:28,999 [main] INFO KieModule was added: FileKieModule[releaseId=org.drools:drools-examples:6.2.0.Final,file=C:\Users\x3.mbetzel\Development\workspaces\jboss-drools\drools-examples-62\target\classes]
> Exception in thread "main" java.lang.RuntimeException: no debugger registered to handle breakpoint
> at org.mvel2.debug.DebuggerContext.checkBreak(DebuggerContext.java:98)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:76)
> at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113)
> at org.mvel2.MVEL.executeExpression(MVEL.java:930)
> at org.drools.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:481)
> at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:77)
> at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:62)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:504)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:379)
> at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:290)
> at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:253)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:370)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:289)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1480)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1422)
> at org.drools.examples.helloworld.HelloWorldExample.main(HelloWorldExample.java:65)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (DROOLS-785) no MVEL debugger registered to handle breakpoint
by Maurice Betzel (JIRA)
[ https://issues.jboss.org/browse/DROOLS-785?page=com.atlassian.jira.plugin... ]
Maurice Betzel commented on DROOLS-785:
---------------------------------------
Using a fresh Neon JBoss Developer Studio, i seem to be missing something here:
package com.sample
dialect "mvel"
import com.sample.DroolsTest.Message;
rule "Hello World"
when
m : Message( status == Message.HELLO, myMessage : message )
then
System.out.println( myMessage );
m.setMessage( "Goodbye cruel world" );
m.setStatus( Message.GOODBYE );
update( m );
end
rule "GoodBye"
when
Message( status == Message.GOODBYE, myMessage : message )
then
System.out.println( myMessage );
end
Results in:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Hello World
Exception executing consequence for rule "Hello World" in com.sample: java.lang.RuntimeException: no debugger registered to handle breakpoint
at org.drools.core.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
at org.drools.core.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1063)
at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:121)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:970)
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1312)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1251)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1359)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1350)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1331)
at com.sample.DroolsTest.main(DroolsTest.java:24)
Caused by: java.lang.RuntimeException: no debugger registered to handle breakpoint
at org.mvel2.debug.DebuggerContext.checkBreak(DebuggerContext.java:98)
at org.mvel2.MVELRuntime.execute(MVELRuntime.java:76)
at org.mvel2.MVEL.executeDebugger(MVEL.java:1059)
at org.drools.core.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:106)
at org.drools.core.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1052)
... 9 more
> no MVEL debugger registered to handle breakpoint
> ------------------------------------------------
>
> Key: DROOLS-785
> URL: https://issues.jboss.org/browse/DROOLS-785
> Project: Drools
> Issue Type: Bug
> Components: core engine, eclipse plugin
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Environment: Win 7 64, JBoss Developer Studio Version: 8.1.0.GA, JBossAS Tools 3.0.3.Final-v20150325-0035-B129, Java 1.7.0_76
> Reporter: Maurice Betzel
> Assignee: Petr Široký
>
> Executing Drools-Examples 6.0.2.Final from github containing MVEL dialect resulted in runtime exception:
> 2015-05-16 14:35:28,603 [main] INFO Found kmodule: file:/C:/Users/x3.mbetzel/Development/workspaces/jboss-drools/drools-examples-62/target/classes/META-INF/kmodule.xml
> 2015-05-16 14:35:28,999 [main] INFO KieModule was added: FileKieModule[releaseId=org.drools:drools-examples:6.2.0.Final,file=C:\Users\x3.mbetzel\Development\workspaces\jboss-drools\drools-examples-62\target\classes]
> Exception in thread "main" java.lang.RuntimeException: no debugger registered to handle breakpoint
> at org.mvel2.debug.DebuggerContext.checkBreak(DebuggerContext.java:98)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:76)
> at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119)
> at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113)
> at org.mvel2.MVEL.executeExpression(MVEL.java:930)
> at org.drools.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:481)
> at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:77)
> at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:62)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:504)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:379)
> at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:290)
> at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:253)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:370)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:289)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1480)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1422)
> at org.drools.examples.helloworld.HelloWorldExample.main(HelloWorldExample.java:65)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-2015) CLI is unable to connect to WildFly management interfaces with undefined security-realm
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2015?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFCORE-2015:
-------------------------------------
Component/s: CLI
> CLI is unable to connect to WildFly management interfaces with undefined security-realm
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-2015
> URL: https://issues.jboss.org/browse/WFCORE-2015
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management, Security
> Affects Versions: 3.0.0.Alpha12
> Reporter: Marek Kopecký
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Alpha13
>
>
> *Description of problem:*
> CLI is unable to connect to EAP with undefined security-realm
> This is regression against EAP 7.0.0, 6.4.0 and 7.1.0.DR7.
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # /core-service=management/management-interface=http-interface:undefine-attribute(name=security-realm)
> # reload
> *Actual results:*
> {noformat}
> [mkopecky@dhcp-10-40-4-180 bin]$ ./jboss-cli.sh -c
> [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:undefine-attribute(name=security-realm)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> [standalone@localhost:9990 /] reload
> Interrupted while pausing before reconnecting.: sleep interrupted
> [disconnected /]
> [mkopecky@dhcp-10-40-4-180 bin]$ ./jboss-cli.sh -c
> Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: Authentication failed: none of the mechanisms presented by the server are supported
> [mkopecky@dhcp-10-40-4-180 bin]$
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-2015) CLI is unable to connect to WildFly management interfaces with undefined security-realm
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2015?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFCORE-2015:
-------------------------------------
Summary: CLI is unable to connect to WildFly management interfaces with undefined security-realm (was: CLI is unable to connect to EAP with undefined security-realm)
> CLI is unable to connect to WildFly management interfaces with undefined security-realm
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-2015
> URL: https://issues.jboss.org/browse/WFCORE-2015
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 3.0.0.Alpha12
> Reporter: Marek Kopecký
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Alpha13
>
>
> *Description of problem:*
> CLI is unable to connect to EAP with undefined security-realm
> This is regression against EAP 7.0.0, 6.4.0 and 7.1.0.DR7.
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # /core-service=management/management-interface=http-interface:undefine-attribute(name=security-realm)
> # reload
> *Actual results:*
> {noformat}
> [mkopecky@dhcp-10-40-4-180 bin]$ ./jboss-cli.sh -c
> [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:undefine-attribute(name=security-realm)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> [standalone@localhost:9990 /] reload
> Interrupted while pausing before reconnecting.: sleep interrupted
> [disconnected /]
> [mkopecky@dhcp-10-40-4-180 bin]$ ./jboss-cli.sh -c
> Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: Authentication failed: none of the mechanisms presented by the server are supported
> [mkopecky@dhcp-10-40-4-180 bin]$
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (ELY-770) Review SASL mechanism handling of isComplete()
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-770:
------------------------------------
Summary: Review SASL mechanism handling of isComplete()
Key: ELY-770
URL: https://issues.jboss.org/browse/ELY-770
Project: WildFly Elytron
Issue Type: Task
Components: SASL
Reporter: Darran Lofthouse
Priority: Critical
Fix For: 1.1.0.Beta15
The javadoc of the isComplete() method states: -
_Determines whether the authentication exchange has completed. This method is typically called after each invocation of evaluateResponse() to determine whether the authentication has completed successfully or should be continued._
Also getAuthorizationID() states: -
_Reports the authorization ID in effect for the client of this session. This method can only be called if isComplete() returns true.
_
Although the former is very vague there just seem to be a suggestion that complete means successfully complete, our mechs are setting complete very early and other wrappers such as AuthenticationCompleteCallbackSaslServerFactory are using complete as a flag to report failures.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7627) Resource adapters subsystem - small user experience enhancements
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-7627?page=com.atlassian.jira.plugin.... ]
Stefano Maestri moved JBEAP-7408 to WFLY-7627:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7627 (was: JBEAP-7408)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JCA
(was: JCA)
(was: User Experience)
Affects Version/s: (was: 7.1.0.DR7)
> Resource adapters subsystem - small user experience enhancements
> ----------------------------------------------------------------
>
> Key: WFLY-7627
> URL: https://issues.jboss.org/browse/WFLY-7627
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Stefano Maestri
> Assignee: Stefano Maestri
> Priority: Minor
> Labels: user_experience
>
> Here's a number of typos or suggestions for user experience enhancements in the {{resource-adapters}} subsystem.
> 1, Schema file ({{docs/schema/wildfly-resource-adapters_4_0.xsd}}) has IMHO bad wording on the {{fair}} element in the complex type {{poolType}}. This is the same as in JBEAP-7018 in the {{datasources}} subsystem.
> 2, (schema file) The same {{fair}} element name is not aligned with the {{pool-fair}} attribute in the {{datasources}} subsystem. Both of these could be called the same ({{pool-fair}}).
> 3, (schema file) {{recover-credential}} element on complex type {{recoverType}} has grammatical mistakes in its description: "Note: if this credential are not specified the security credential are used for recover too" -> "Note: if this credential is not specified the security credential is used for recovery too"
> 4, (subsystem from now on) {{background validation}} on {{connection-definitions}} says it requires server restarts, but its {{restart-required}} value is {{no-services}}. Doing {{/subsystem=resource-adapters/resource-adapter=new-resource-adapter/connection-definitions=new-connection-definition:write-attribute(name=background-validation,value=false)}} does not prompt the user to restart the server.
> 5, The same goes for {{background-validation-millis}}: {{/subsystem=resource-adapters/resource-adapter=new-resource-adapter/connection-definitions=new-connection-definition:write-attribute(name=background-validation-millis,value=12000)}}
> 6, The same goes for {{idle-timeout-minutes}}: {{/subsystem=resource-adapters/resource-adapter=new-resource-adapter/connection-definitions=new-connection-definition:write-attribute(name=idle-timeout-minutes,value=4)}}
> 7, The same goes for {{pool-prefill}}: {{/subsystem=resource-adapters/resource-adapter=new-resource-adapter/connection-definitions=new-connection-definition:write-attribute(name=pool-prefill,value=true)}}
> 8, {{idle-timeout-millis}} can be lower than zero:
> {{/subsystem=resource-adapters/resource-adapter=new-resource-adapter/connection-definitions=new-connection-definition:write-attribute(name=idle-timeout-minutes,value=-4)}}
> 9, {{flush-strategy}} on {{connection-definitions}} has bad valid values in its description - this is the same as in the {{datasources}} subsystem - JBEAP-7018
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months