[JBoss JIRA] (WFCORE-1544) IfElseControlFlow ifRequest is not validated
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-1544?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-1544:
----------------------------------------------
Validating this request could change the behavior of if command and impact existing scripts. This would require the introduction of a new system property to explicitly validate the if request. Seems a corner case for which we didn't get user report. Closing it at will not fix.
> IfElseControlFlow ifRequest is not validated
> --------------------------------------------
>
> Key: WFCORE-1544
> URL: https://issues.jboss.org/browse/WFCORE-1544
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Major
>
> IfElseControlFlow.run sends the if request without validation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFCORE-1545) File path to file content replacement is bound to validation
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-1545?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise closed WFCORE-1545.
----------------------------------------
Resolution: Won't Fix
> File path to file content replacement is bound to validation
> ------------------------------------------------------------
>
> Key: WFCORE-1545
> URL: https://issues.jboss.org/browse/WFCORE-1545
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Major
>
> DefaultBatch and OperationRequestHandler are making the replacement only if validation is enabled.
> It seems that users are expecting the replacement to be done in all cases.
> Doing so we would make operation description retrieval mandatory for all requests. This could have an impact on the CLI performance.
> We should have a configuration option to disable the replacement. By default the replacement should be enabled. With validation OFF and replacement OFF, we would have no extra requests sent by the CLI.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFCORE-1545) File path to file content replacement is bound to validation
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-1545?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-1545:
----------------------------------------------
The current logic makes sense. In order to be able to do file path to BYTES replacement, we need to retrieve the operation metadata. Introduce new options to cover this corner case would be overkill. We shouldn't fix it and keep the current behavior.
> File path to file content replacement is bound to validation
> ------------------------------------------------------------
>
> Key: WFCORE-1545
> URL: https://issues.jboss.org/browse/WFCORE-1545
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Major
>
> DefaultBatch and OperationRequestHandler are making the replacement only if validation is enabled.
> It seems that users are expecting the replacement to be done in all cases.
> Doing so we would make operation description retrieval mandatory for all requests. This could have an impact on the CLI performance.
> We should have a configuration option to disable the replacement. By default the replacement should be enabled. With validation OFF and replacement OFF, we would have no extra requests sent by the CLI.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFCORE-417) jboss-cli should set -Djava.awt.headless=true
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-417?page=com.atlassian.jira.plugin... ]
Jean-Francois Denise commented on WFCORE-417:
---------------------------------------------
I am on Mac OSX High Sierra + JDK 1.8_121. I have created a script that creates 1000000 system-properties. During jboss CLI script execution the focus doesn't shift back to the terminal in which the CLI is running. I can't reproduce the issue. Closing it. Feel free to re-open if you still observe it.
> jboss-cli should set -Djava.awt.headless=true
> ---------------------------------------------
>
> Key: WFCORE-417
> URL: https://issues.jboss.org/browse/WFCORE-417
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Robin Rosenberg
> Assignee: Jean-Francois Denise
> Priority: Minor
>
> On OS X using jboss-cli.sh will cause focus to shift making it very inconvenient to do other things while scripts that talk to jboss execute.
> There is a workaround: export JAVA_OPTS=-Djava.awt.headless=true before invoking the cli, but I see no reason for the CLI not do this itself. This also applied to the adduser.sh script.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFCORE-417) jboss-cli should set -Djava.awt.headless=true
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-417?page=com.atlassian.jira.plugin... ]
Jean-Francois Denise closed WFCORE-417.
---------------------------------------
Resolution: Cannot Reproduce
> jboss-cli should set -Djava.awt.headless=true
> ---------------------------------------------
>
> Key: WFCORE-417
> URL: https://issues.jboss.org/browse/WFCORE-417
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Robin Rosenberg
> Assignee: Jean-Francois Denise
> Priority: Minor
>
> On OS X using jboss-cli.sh will cause focus to shift making it very inconvenient to do other things while scripts that talk to jboss execute.
> There is a workaround: export JAVA_OPTS=-Djava.awt.headless=true before invoking the cli, but I see no reason for the CLI not do this itself. This also applied to the adduser.sh script.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (ELY-409) Certificate Authority
by Boleslaw Dawidowicz (Jira)
[ https://issues.jboss.org/browse/ELY-409?page=com.atlassian.jira.plugin.sy... ]
Boleslaw Dawidowicz updated ELY-409:
------------------------------------
Labels: idm (was: )
> Certificate Authority
> ---------------------
>
> Key: ELY-409
> URL: https://issues.jboss.org/browse/ELY-409
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Certificate Authority
> Reporter: Darran Lofthouse
> Priority: Major
> Labels: idm
>
> This is a top level task to consider what we will need for certificate authority use within Elytron.
> I would imagine we would start with a fairly simple implementation ourselves within Elytron that can handle signing with the appropriate constraint checking / management of signed certificates, we would also want revocation, CRL generation, a simple OCSP responder.
> From this we will have an API so that CA functions can be requested from within the application server, we will also have an SPI so that we can integrate with different CAs as an example FreeIPA.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months