[JBoss JIRA] (WFLY-10188) Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration
by Jan Stourac (JIRA)
[ https://issues.jboss.org/browse/WFLY-10188?page=com.atlassian.jira.plugin... ]
Jan Stourac updated WFLY-10188:
-------------------------------
Affects Version/s: 13.0.0.Final
14.0.1.Final
> Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10188
> URL: https://issues.jboss.org/browse/WFLY-10188
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Pavel Jelinek
> Assignee: Stuart Douglas
> Priority: Critical
>
> Undertow server needs default-host to be set to be able to be used as Undertow subsystem default-server otherwise Wildfly would not start due to:
> {code}
> ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=undertow' are not available:
> org.wildfly.undertow.host.test-server.default-host; Possible registration points for this capability:
> /subsystem=undertow/server=*/host=*
> {code}
> This is dangerous as after calling a {{reload}} operation, the server simply fails and crashes. One can accidentaly kill the server with this and \!manual\! fix is necessary to the configuration to be able to start server again.
> I think that there should be some check that configuration of the newly created server is complete and valid before it is set as a default server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (WFLY-11096) Stale session data on failover
by tommaso borgato (JIRA)
tommaso borgato created WFLY-11096:
--------------------------------------
Summary: Stale session data on failover
Key: WFLY-11096
URL: https://issues.jboss.org/browse/WFLY-11096
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 14.0.1.Final, 15.0.0.Alpha1
Reporter: tommaso borgato
Assignee: Paul Ferraro
Priority: Minor
Occured on client. Affected scenarios:
eap-7x-failover-ejb-ejbservlet-shutdown-dist-async
eap-7x-failover-http-granular-shutdown-repl-sync
eap-7x-failover-http-session-jvmkill-dist-sync
eap-7x-failover-http-session-jvmkill-repl-sync
eap-7x-failover-http-session-shutdown-repl-sync-haproxy
eap-7x-failover-http-session-undeploy-dist-sync
Client log stacktrace:
{code}
2016/09/21 17:28:51:294 EDT [WARN ][Runner - 134] HOST dev220.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 42, received 41, Runner: 134>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 42, received 41, Runner: 134
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:745)
{code}
Link to client log:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ELY-867) Masked password support cryptography usage
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-867?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse reassigned ELY-867:
------------------------------------
Assignee: (was: Jan Kalina)
> Masked password support cryptography usage
> ------------------------------------------
>
> Key: ELY-867
> URL: https://issues.jboss.org/browse/ELY-867
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Passwords
> Reporter: Zoran Regvart
>
> I encountered couple of issues with cryptography used for password masking:
> * implementation of masked passwords drops initialization vector (IV) randomly generated by the {{javax.crypto.Cipher}} which makes unmasking (decryption) impossible.
> * the implementation is using the same algorithm for key derivation and encryption, which is not possible as there is no encryption support in {{javax.crypto.Cipher}} for PKDBF2 family of algorithms, they are supported only in {{javax.crypto.SecretKeyFactory}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ELY-1291) Coverity static analysis: Non-Serializable SecurityIdentity is contained in Serializable ElytronAccount
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1291?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse reassigned ELY-1291:
-------------------------------------
Assignee: (was: Jan Kalina)
> Coverity static analysis: Non-Serializable SecurityIdentity is contained in Serializable ElytronAccount
> -------------------------------------------------------------------------------------------------------
>
> Key: ELY-1291
> URL: https://issues.jboss.org/browse/ELY-1291
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Martin Choma
>
> Coverity static analysis found Serializable ElytronAccount contains non-Serializable SecurityIdentity.
> https://scan7.coverity.com/reports.htm#v23632/p12664/fileInstanceId=86223...
> Please resolve this inconsistent situation.
> By dev feedback SecurityIdentity can't be made Serializable. Rework to remove SecurityIdentity from ElytronAccount was suggested.
> {code:title=hipchat.log}
> [3:23 PM] Martin Choma: Shouldn't be SecurityIdentity Serializable? - because of HttpSession replication?
> [3:23 PM] Darran Lofthouse: No it can't be
> [3:24 PM] Darran Lofthouse: it is backed by implementation as well as state
> [3:25 PM] David M. Lloyd: right it would essentially be a security hole to be able to deserialize an identity
> [3:26 PM] David M. Lloyd: among other problems
> [3:26 PM] Darran Lofthouse: on the far side we restore the identity instead of deserializing it
> [3:31 PM] Martin Choma: I got it. Thing is static analyzer is complaining elytron-web ElytronAccount (Serializable class) is referencing SecurityIdentity, but probably problem is ElytronAccount does not have to be mark as Serializable, right?
> [3:34 PM] Darran Lofthouse: @MartinChoma we may be able to re-work that and remove the reference to SI
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months