[JBoss JIRA] (WFLY-7429) configurable-sasl-server-factory cannot set mechanism information
by Jan Kalina (JIRA)
Jan Kalina created WFLY-7429:
--------------------------------
Summary: configurable-sasl-server-factory cannot set mechanism information
Key: WFLY-7429
URL: https://issues.jboss.org/browse/WFLY-7429
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Jan Kalina
Assignee: Jan Kalina
sasl-authentication-factory and sasl-server-factory creates chain of SaslServerFactories - for example ServerNameSaslServerFactory only delegates creating to following factory in chain but with rewriting of the server name.
In this chain is also *SetMechanismInformationSaslServerFactory*, which call callback handler to send MechanismInformation into ServerAuthenticationContext - there it will cause state change from InactiveState to InitialState.
*The problem is,* if the configurable-sasl-server-factory is used, the *SetMechanismInformationSaslServerFactory* is in chain twice. The first occurence (by sasl-authentication-factory) will cause change state to InitialState, but before the serverName+protocol is overriden by SaslServerFactories following in chain. The second occurence (by configurable-sasl-server-factory) already have serverName+protocol set, but because the ServerAuthenticationContext is already in InitialState, the exception "Too late to set" is thrown and createSaslServer returns null - fail completely.
The chain of SaslServerFactories:
{code:java}
AuthenticationTimeoutSSF
TrustManagerSSF
AuthenticationCompleteSSF
SetMechanismInformationSSF => cbh => InactiveState -> InitialState(undefined, null)
ServerNameSSF
ProtocolSSF
SetMechanismInformationSSF => cbh => "Too late to set" => return null
SecurityProviderSSF
{code}
Will have to discuss yet how to correctly solve this... (maybe consider allowing of multiple MechanismInformation setting? In current design the sasl-authentication-factory cannot detect the configurable-sasl-server-factory WILL change the MechanismInformation yet...)
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 2 months
[JBoss JIRA] (ELY-702) configurable-sasl-server-factory cannot set mechanism information
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-702?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina moved WFLY-7429 to ELY-702:
--------------------------------------
Project: WildFly Elytron (was: WildFly)
Key: ELY-702 (was: WFLY-7429)
Component/s: Authentication Client
(was: Security)
> configurable-sasl-server-factory cannot set mechanism information
> -----------------------------------------------------------------
>
> Key: ELY-702
> URL: https://issues.jboss.org/browse/ELY-702
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> sasl-authentication-factory and sasl-server-factory creates chain of SaslServerFactories - for example ServerNameSaslServerFactory only delegates creating to following factory in chain but with rewriting of the server name.
> In this chain is also *SetMechanismInformationSaslServerFactory*, which call callback handler to send MechanismInformation into ServerAuthenticationContext - there it will cause state change from InactiveState to InitialState.
> *The problem is,* if the configurable-sasl-server-factory is used, the *SetMechanismInformationSaslServerFactory* is in chain twice. The first occurence (by sasl-authentication-factory) will cause change state to InitialState, but before the serverName+protocol is overriden by SaslServerFactories following in chain. The second occurence (by configurable-sasl-server-factory) already have serverName+protocol set, but because the ServerAuthenticationContext is already in InitialState, the exception "Too late to set" is thrown and createSaslServer returns null - fail completely.
> The chain of SaslServerFactories:
> {code:java}
> AuthenticationTimeoutSSF
> TrustManagerSSF
> AuthenticationCompleteSSF
> SetMechanismInformationSSF => cbh => InactiveState -> InitialState(undefined, null)
> ServerNameSSF
> ProtocolSSF
> SetMechanismInformationSSF => cbh => "Too late to set" => return null
> SecurityProviderSSF
> {code}
> Will have to discuss yet how to correctly solve this... (maybe consider allowing of multiple MechanismInformation setting? In current design the sasl-authentication-factory cannot detect the configurable-sasl-server-factory WILL change the MechanismInformation yet...)
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 2 months
[JBoss JIRA] (WFLY-7428) Add ExtendedJBossXATerminator service to the transactions subsystem
by Gytis Trikleris (JIRA)
Gytis Trikleris created WFLY-7428:
-------------------------------------
Summary: Add ExtendedJBossXATerminator service to the transactions subsystem
Key: WFLY-7428
URL: https://issues.jboss.org/browse/WFLY-7428
Project: WildFly
Issue Type: Enhancement
Components: Transactions
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 11.0.0.Alpha1
ExtendedJBossXATerminator from Narayana SPI is not currently injectable as a service. However, it is needed to check if the specific transaction is available in the server.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 2 months
[JBoss JIRA] (WFLY-7389) Improve undefined statistics-enabled attribute testing in infinispan subsystem for EAP 6.2
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-7389?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-7389:
---------------------------------
Summary: Improve undefined statistics-enabled attribute testing in infinispan subsystem for EAP 6.2 (was: Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2)
> Improve undefined statistics-enabled attribute testing in infinispan subsystem for EAP 6.2
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-7389
> URL: https://issues.jboss.org/browse/WFLY-7389
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> The test file clustering/infinispan/extension/src/test/resources/org/jboss/as/clustering/infinispan/subsystem/infinispan-transformer-reject.xml specifies {code}statistics-enabled="false"{code} for all caches and cache-containers thus the situation when its undefined is never tested.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 2 months
[JBoss JIRA] (WFLY-7426) Attempt to remove cache container with default-cache defined throws NPE
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-7426?page=com.atlassian.jira.plugin.... ]
Paul Ferraro moved JBEAP-6743 to WFLY-7426:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7426 (was: JBEAP-6743)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: 10.1.0.Final
(was: 7.1.0.DR7)
> Attempt to remove cache container with default-cache defined throws NPE
> -----------------------------------------------------------------------
>
> Key: WFLY-7426
> URL: https://issues.jboss.org/browse/WFLY-7426
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Minor
>
> When I create a local cache as a child of some cache container and then set it to that cache container as its default cache, it is impossible to remove that cache container.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
8 years, 2 months