[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-849:
---------------------------------
Fix Version/s: 1.1.0.Beta21
(was: 1.1.0.Beta20)
> Rename setMechanismProperties to setSaslMechanismProperties
> -----------------------------------------------------------
>
> Key: ELY-849
> URL: https://issues.jboss.org/browse/ELY-849
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 1.1.0.Beta21
>
>
> If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties.
> We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7912) It's not possible to change election-policy of singleton-policy
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-7912?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-7912:
------------------------------------
I agree that the above set of commands *should* work. I'll look into it.
Until then, you can change the election policy of a singleton policy via:
/subsystem=singleton/singleton-policy=default/election-policy=random:add()
Since only 1 election policy is allowed for a given singleton policy, the add will operate like a replace.
> It's not possible to change election-policy of singleton-policy
> ---------------------------------------------------------------
>
> Key: WFLY-7912
> URL: https://issues.jboss.org/browse/WFLY-7912
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Tomas Hofman
> Assignee: Paul Ferraro
>
> Attempt to change election policy:
> {code}
> [standalone@localhost:9990 /] batch
> [standalone@localhost:9990 / #] /subsystem=singleton/singleton-policy=default/election-policy=simple:remove
> [standalone@localhost:9990 / #] /subsystem=singleton/singleton-policy=default/election-policy=random:add
> [standalone@localhost:9990 / #] run-batch
> {code}
> results in
> {code}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
> WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
> Step: step-2
> Operation: /subsystem=singleton/singleton-policy=default/election-policy=random:add
> Failure: WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.singleton.policy.default.election-policy is already registered
> {code}
> The bug seems to be introduced by https://github.com/wildfly/wildfly/commit/605b22c30ae122492e7c019e330fea2...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months