[JBoss JIRA] (WFLY-8025) Alternatives attribute "domain" doesn't exist in modcluster subsystem
by Claudio Miranda (JIRA)
Claudio Miranda created WFLY-8025:
-------------------------------------
Summary: Alternatives attribute "domain" doesn't exist in modcluster subsystem
Key: WFLY-8025
URL: https://issues.jboss.org/browse/WFLY-8025
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Reporter: Claudio Miranda
Assignee: Radoslav Husar
modcluster resource contains the following attribute definition for "load-balancing-group"
{code}
"load-balancing-group" => {
"type" => STRING,
"description" => "loadBalancingGroup name.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"alternatives" => ["domain"],
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
{code}
But the alternatives constraint specifies a "domain" attribute that doesn't exist.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (ELY-919) Coverity: default platform encoding used in DefaultSingleSignOnSessionFactory
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/ELY-919?page=com.atlassian.jira.plugin.sy... ]
Ilia Vassilev moved WFLY-7953 to ELY-919:
-----------------------------------------
Project: WildFly Elytron (was: WildFly)
Key: ELY-919 (was: WFLY-7953)
Component/s: HTTP
(was: Security)
Affects Version/s: 1.1.0.Beta21
(was: 11.0.0.Alpha1)
> Coverity: default platform encoding used in DefaultSingleSignOnSessionFactory
> -----------------------------------------------------------------------------
>
> Key: ELY-919
> URL: https://issues.jboss.org/browse/ELY-919
> Project: WildFly Elytron
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 1.1.0.Beta21
> Reporter: Martin Choma
> Assignee: Ilia Vassilev
> Priority: Critical
>
> Coverity static-analysis scan found a String to byte conversion (4xoccurences of {{getBytes()}}) with default platform encoding in the DefaultSingleSignOnSessionFactory method.
> Following code
> {code:java|title=DefaultSingleSignOnSessionFactory.java}
> @Override
> public String createLogoutParameter(String sessionId) {
> try {
> Signature signature = Signature.getInstance(DEFAULT_SIGNATURE_ALGORITHM);
> signature.initSign(this.privateKey);
> Base64.Encoder urlEncoder = Base64.getUrlEncoder();
> return sessionId + "." + ByteIterator.ofBytes(urlEncoder.encode(ByteIterator.ofBytes(sessionId.getBytes()).sign(signature).drain())).asUtf8String().drainToString();
> } catch (NoSuchAlgorithmException | InvalidKeyException e) {
> throw new IllegalStateException(e);
> }
> }
>
> @Override
> public String verifyLogoutParameter(String parameter) {
> String[] parts = parameter.split("\\.");
> if (parts.length != 2) {
> throw new IllegalArgumentException(parameter);
> }
> try {
> String localSessionId = ByteIterator.ofBytes(parts[0].getBytes()).asUtf8String().drainToString();
> Signature signature = Signature.getInstance(DEFAULT_SIGNATURE_ALGORITHM);
> signature.initVerify(this.certificate);
> signature.update(localSessionId.getBytes());
> Base64.Decoder urlDecoder = Base64.getUrlDecoder();
> if (!ByteIterator.ofBytes(urlDecoder.decode(parts[1].getBytes())).verify(signature)) {
> throw log.httpMechSsoInvalidLogoutMessage(localSessionId);
> }
> return localSessionId;
> } catch (NoSuchAlgorithmException | InvalidKeyException e) {
> throw new IllegalStateException(e);
> } catch (SignatureException e) {
> throw new IllegalArgumentException(parameter, e);
> }
> }
> {code}
> The encoding should be specified as argument.
> Setting with high priority, because once default platform encoding UTF-16 will be set, funcionality do not need to work as intended. Especially when combined with {{asUtf8String()}}, which implies specifying default encoding UTF-8.
> https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=86758...
> https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=86758...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (ELY-918) Allow HTTP mechanisms to decide if response should be sent when authentication is in progress
by Pedro Igor (JIRA)
Pedro Igor created ELY-918:
------------------------------
Summary: Allow HTTP mechanisms to decide if response should be sent when authentication is in progress
Key: ELY-918
URL: https://issues.jboss.org/browse/ELY-918
Project: WildFly Elytron
Issue Type: Enhancement
Components: HTTP
Affects Versions: 1.1.0.Beta21
Reporter: Pedro Igor
Assignee: Pedro Igor
Currently, mechanisms are not allowed to decide if a challenge should be sent or not when processing a request to path where authentication is not required.
Currently, we always write to the response regardless if authentication if required or not, making impossible to mechanisms decide what you do in cases where a request is a for a non-protected resource and an authentication challenge should not be sent.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months