[JBoss JIRA] (DROOLS-1480) Support timezones in date and type variables
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-1480:
-------------------------------------
Summary: Support timezones in date and type variables
Key: DROOLS-1480
URL: https://issues.jboss.org/browse/DROOLS-1480
Project: Drools
Issue Type: Enhancement
Components: dmn engine
Affects Versions: 7.0.0.Beta7
Reporter: Tibor Zimányi
Assignee: Edson Tirelli
Priority: Minor
Currently we don't support timezones in date and time variables. This should be implemented, when we are sure about the exact format of timezones.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1010) Additional TRACE logging for MechanismInformationCallback
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-1010:
-------------------------------------
Summary: Additional TRACE logging for MechanismInformationCallback
Key: ELY-1010
URL: https://issues.jboss.org/browse/ELY-1010
Project: WildFly Elytron
Issue Type: Task
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Minor
Fix For: 1.1.0.Beta32
Debugging a current issue it would be very helpful within the log to see the MechanismInformation that the callback is transporting.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1009) Default settings of SSL session caching for Elytron *-ssl-context are not safe
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/ELY-1009?page=com.atlassian.jira.plugin.s... ]
Ilia Vassilev moved JBEAP-9633 to ELY-1009:
-------------------------------------------
Project: WildFly Elytron (was: JBoss Enterprise Application Platform)
Key: ELY-1009 (was: JBEAP-9633)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: SSL
(was: Security)
Affects Version/s: 1.1.0.Beta29
(was: 7.1.0.DR13)
> Default settings of SSL session caching for Elytron *-ssl-context are not safe
> ------------------------------------------------------------------------------
>
> Key: ELY-1009
> URL: https://issues.jboss.org/browse/ELY-1009
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.1.0.Beta29
> Reporter: Ilia Vassilev
> Assignee: Ilia Vassilev
> Priority: Critical
> Labels: default, management-model, ssl, tls
>
> The default values of {{maximum-session-cache-size}} and {{session-timeout}} of Elytron {{*-ssl-context}} are {{0}}. This is not safe because SSL sessions can be stored indefinitely. Furthermore, such default settings overwrites default settings in Java, which can be unexpected.
> There should be reasonable combination of values, or Java default values should be (let) used.
> For example, see http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2547) Revisit the meaning of aggregate-principal-transformer
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFCORE-2547:
------------------------------------
Summary: Revisit the meaning of aggregate-principal-transformer
Key: WFCORE-2547
URL: https://issues.jboss.org/browse/WFCORE-2547
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Critical
Meaning of Elytron {{aggregate-principal-transformer}} should be revised. Also one point about {{regex-validating-principal-transformer}} is included since it seems its use cases are related to aggregate-principal-transformer. See:
* It seems that it works like "It iterates through assigned Principal Transformers and returns the first non-null transformed Principal" - is it correct and intended behaviour? Is "aggregate-principal-transformer" appropriate name for transformer which works like that?
* What is the use case for regex-validating-principal-transformer. This transformer just checks some pattern and if it does not match then it rewrites Principal name to null. I think it can be useful in aggregate-principal-transformer, when it can check that name matches some pattern in first transformer (regex-validating-principal-transformer) and then transforms principal in another transformer (e.g. constant-principal-transformer). Is there any other use case?
* When can aggregate-principal-transformer return any other Principal Transformer than first of the list? I think only user implemented custom-principal-transformer can currently return null (which enable iterating to another principal transformer in the list). Also regex-validating-principal-transformer can be used for returning non-first transformer, as I mentioned in previous point. Is there any real scenario when aggregate-principal-transformer can be used?
This issue is reported based on previous discussion with engineering.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1008) Elytron Audit Logging does not support logging into more destinations
by Jan Tymel (JIRA)
Jan Tymel created ELY-1008:
------------------------------
Summary: Elytron Audit Logging does not support logging into more destinations
Key: ELY-1008
URL: https://issues.jboss.org/browse/ELY-1008
Project: WildFly Elytron
Issue Type: Bug
Reporter: Jan Tymel
Assignee: Darran Lofthouse
Priority: Blocker
Attachments: deployment.war
According to my understanding it is not possible to send Elytron Audit logs to more destinations (files or syslogs). It is caused by {{security-event-listener}} property within {{security-domain}} takes only _string_ attribute and not _list_ of them.
Example of use-case that may be affected:
I want to send logs to a syslog server AND also as a backup to a file on NFS. This means that if the syslog server will be unreachable, it will still be possible to send logs into a backup file on NFS and therefore no logs will be completely lost.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1008) Elytron Audit Logging does not support logging into more destinations
by Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/ELY-1008?page=com.atlassian.jira.plugin.s... ]
Jan Tymel reassigned ELY-1008:
------------------------------
Assignee: (was: Darran Lofthouse)
> Elytron Audit Logging does not support logging into more destinations
> ---------------------------------------------------------------------
>
> Key: ELY-1008
> URL: https://issues.jboss.org/browse/ELY-1008
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Jan Tymel
> Priority: Blocker
> Attachments: deployment.war
>
>
> According to my understanding it is not possible to send Elytron Audit logs to more destinations (files or syslogs). It is caused by {{security-event-listener}} property within {{security-domain}} takes only _string_ attribute and not _list_ of them.
> Example of use-case that may be affected:
> I want to send logs to a syslog server AND also as a backup to a file on NFS. This means that if the syslog server will be unreachable, it will still be possible to send logs into a backup file on NFS and therefore no logs will be completely lost.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1008) Elytron Audit Logging does not support logging into more destinations
by Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/ELY-1008?page=com.atlassian.jira.plugin.s... ]
Jan Tymel updated ELY-1008:
---------------------------
Attachment: deployment.war
> Elytron Audit Logging does not support logging into more destinations
> ---------------------------------------------------------------------
>
> Key: ELY-1008
> URL: https://issues.jboss.org/browse/ELY-1008
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Jan Tymel
> Priority: Blocker
> Attachments: deployment.war
>
>
> According to my understanding it is not possible to send Elytron Audit logs to more destinations (files or syslogs). It is caused by {{security-event-listener}} property within {{security-domain}} takes only _string_ attribute and not _list_ of them.
> Example of use-case that may be affected:
> I want to send logs to a syslog server AND also as a backup to a file on NFS. This means that if the syslog server will be unreachable, it will still be possible to send logs into a backup file on NFS and therefore no logs will be completely lost.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month