[JBoss JIRA] (ELY-1380) Calling getNegotiatedProperty for Elytron SASL mechanisms doesn't throw IllegalStateException when negotiatition is not completed
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1380?page=com.atlassian.jira.plugin.s... ]
Jan Kalina moved JBEAP-13360 to ELY-1380:
-----------------------------------------
Project: WildFly Elytron (was: JBoss Enterprise Application Platform)
Key: ELY-1380 (was: JBEAP-13360)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: SASL
(was: Security)
Affects Version/s: 1.2.0.Beta4
(was: 7.1.0.CR2)
> Calling getNegotiatedProperty for Elytron SASL mechanisms doesn't throw IllegalStateException when negotiatition is not completed
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1380
> URL: https://issues.jboss.org/browse/ELY-1380
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SASL
> Affects Versions: 1.2.0.Beta4
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
>
> The Elytron SASL mechanism implementations don't throw {{IllegalStateException}} when calling the {{getNegotiatedProperty()}} method before the negotiation is finished.
> The contract of the {{Object javax.security.sasl.SaslClient.getNegotiatedProperty(String propName)}} says:
> bq. Retrieves the negotiated property. This method can be called only after the authentication exchange has completed (i.e., when isComplete() returns true); otherwise, an IllegalStateException is thrown.
> The same is valid for the {{SaslServer}} interface.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (ELY-1379) KeyStore element does not support overriding Provider discovery
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-1379:
-------------------------------------
Summary: KeyStore element does not support overriding Provider discovery
Key: ELY-1379
URL: https://issues.jboss.org/browse/ELY-1379
Project: WildFly Elytron
Issue Type: Enhancement
Components: Authentication Client
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.2.0.Beta5
Additionally it doesn't take into account the default Provider discovery or the Provider definition at the root of the <authentication-configuration /> definition.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (ELY-1378) KeyStore resource does not support specifying the module
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-1378:
-------------------------------------
Summary: KeyStore resource does not support specifying the module
Key: ELY-1378
URL: https://issues.jboss.org/browse/ELY-1378
Project: WildFly Elytron
Issue Type: Enhancement
Components: Authentication Client
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.2.0.Beta5
In other areas of the authentication configuration where the ClassLoader is used we allow an optional module to be specified, we don't do this for <keyStore><resource/><keyStore> which only accepts a name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.
by Walter Medvedeo (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ]
Walter Medvedeo edited comment on DROOLS-1748 at 10/4/17 8:54 AM:
------------------------------------------------------------------
For domain installations the following additional configurations are required.
# the profile name that is being used, e.g. full, default, etc.
datasource.management.wildfly.profile=full
# the server group name to which the current kie-wb installation belongs. e.g:
datasource.management.wildfly.serverGroup=primary-server-group
# Internal kie-wb component configuration for domain configurations
datasource.management.DefChangeHandler=DomainModeChangeHandler
The profile and serverGroup name to use can be found in the hosts.xml configuration file in a section like this:
<server-groups>
<server-group name="primary-server-group" profile="full">
<jvm name="default">
<heap size="1000m" max-size="1000m"/>
</jvm>
<socket-binding-group ref="full-sockets"/>
<deployments>
<deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/>
</deployments>
</server-group>
All this 3 mentioned properties must be added to the datasource-management.properties file found in the:
kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties
was (Author: wmedvede):
For domain installations the following additional configurations are required.
# the profile name that is being used, e.g. full, default, etc.
datasource.management.wildfly.profile=full
# the server group name to with the current kie-wb installation belongs. e.g:
datasource.management.wildfly.serverGroup=primary-server-group
# Internal kie-wb component configuration for domain configurations
datasource.management.DefChangeHandler=DomainModeChangeHandler
The profile and serverGroup name can be found in the hosts.xml configuration file in a section like this:
<server-groups>
<server-group name="primary-server-group" profile="full">
<jvm name="default">
<heap size="1000m" max-size="1000m"/>
</jvm>
<socket-binding-group ref="full-sockets"/>
<deployments>
<deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/>
</deployments>
</server-group>
All this 3 mentioned properties should added to the datasource-management.properties file found in the:
kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties
> Drools workbench datasource on Wildfly domain.
> ----------------------------------------------
>
> Key: DROOLS-1748
> URL: https://issues.jboss.org/browse/DROOLS-1748
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Final, 7.3.0.Final
> Environment: Drools workbench on Wildfly domain cluster
> Reporter: M C
> Assignee: Petr Široký
> Priority: Critical
>
> After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source.
> [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")]
> Problem does not affect Wildfly standalone configuration, only domain configuration using profiles.
> WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/...
> In standalone syntax is: /subsystem=datasource/.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.
by Walter Medvedeo (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ]
Walter Medvedeo commented on DROOLS-1748:
-----------------------------------------
For domain installations the following additional configurations are required.
# the profile name that is being used, e.g. full, default, etc.
datasource.management.wildfly.profile=full
# the server group name to with the current kie-wb installation belongs. e.g:
datasource.management.wildfly.serverGroup=primary-server-group
# Internal kie-wb component configuration for domain configurations
datasource.management.DefChangeHandler=DomainModeChangeHandler
The profile and serverGroup name can be found in the hosts.xml configuration file in a section like this:
<server-groups>
<server-group name="primary-server-group" profile="full">
<jvm name="default">
<heap size="1000m" max-size="1000m"/>
</jvm>
<socket-binding-group ref="full-sockets"/>
<deployments>
<deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/>
</deployments>
</server-group>
All this 3 mentioned properties should added to the datasource-management.properties file found in the:
kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties
> Drools workbench datasource on Wildfly domain.
> ----------------------------------------------
>
> Key: DROOLS-1748
> URL: https://issues.jboss.org/browse/DROOLS-1748
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Final, 7.3.0.Final
> Environment: Drools workbench on Wildfly domain cluster
> Reporter: M C
> Assignee: Petr Široký
> Priority: Critical
>
> After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source.
> [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")]
> Problem does not affect Wildfly standalone configuration, only domain configuration using profiles.
> WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/...
> In standalone syntax is: /subsystem=datasource/.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9417) No default-response-code during deployment sent
by Nero M (JIRA)
Nero M created WFLY-9417:
----------------------------
Summary: No default-response-code during deployment sent
Key: WFLY-9417
URL: https://issues.jboss.org/browse/WFLY-9417
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 11.0.0.CR1
Reporter: Nero M
Assignee: Stuart Douglas
Fix For: 11.0.0.Final
Hi, i am experiencing a strange behaviour with WF11 which was not like this on WF10.
When a *.dodeploy file exists during server-start. The Default response code
e.g.
<host name="default-host" alias="localhost" default-response-code="503">
Is not sent during the time of deployment. Instead any requests goes into a pending state with (seemingly) no timeout.
If the *.dodeploy file is created AFTER the server boots up, the default response code is sent until the deployment is complete.
(After this line): WFLYSRV0025: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.4.Final) started in 6468ms
I think the server should not "hang" during the deployment-time, just like it was on WF10.
Is there anything which has to be changed in the standalone xml between 10 and 11 to get the same behaviour?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months