[JBoss JIRA] (WFCORE-5151) dir-contexts referral-mode attribute upper/lower case discrepancy
by Ricardo Martin Camarero (Jira)
[ https://issues.redhat.com/browse/WFCORE-5151?page=com.atlassian.jira.plug... ]
Ricardo Martin Camarero reassigned WFCORE-5151:
-----------------------------------------------
Assignee: Ricardo Martin Camarero
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFCORE-5151
> URL: https://issues.redhat.com/browse/WFCORE-5151
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 13.0.0.Beta6
> Reporter: Jan Stourac
> Assignee: Ricardo Martin Camarero
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFCORE-5147) Add TRACE / DEBUG logging for git integration
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5147?page=com.atlassian.jira.plug... ]
Darran Lofthouse commented on WFCORE-5147:
------------------------------------------
Also messages that are logged at Level.INFO are missing message IDs
> Add TRACE / DEBUG logging for git integration
> ---------------------------------------------
>
> Key: WFCORE-5147
> URL: https://issues.redhat.com/browse/WFCORE-5147
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 14.0.0.Beta1
>
>
> The initial load can likely be at DEBUG level but ongoing persist calls should likely be at TRACE as they would be per model update.
> Trying to debug some failures in the test case org.jboss.as.test.manualmode.management.persistence.RemoteSshGitRepositoryTestCase when executed using GitHub actions some messages from jgit seem missing but as there is no debug or trace logging around our use of jgit it is not clear if that logging is missing because jgit is not being called or if the messages are not getting flushed to the logs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFCORE-5151) dir-contexts referral-mode attribute upper/lower case discrepancy
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5151?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-5151:
-------------------------------------
Affects Version/s: 13.0.0.Beta6
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFCORE-5151
> URL: https://issues.redhat.com/browse/WFCORE-5151
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 13.0.0.Beta6
> Reporter: Jan Stourac
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFCORE-5151) dir-contexts referral-mode attribute upper/lower case discrepancy
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5151?page=com.atlassian.jira.plug... ]
Darran Lofthouse moved WFLY-13935 to WFCORE-5151:
-------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-5151 (was: WFLY-13935)
Component/s: Security
(was: Security)
Affects Version/s: (was: 15.0.0.Final)
(was: 16.0.0.Final)
(was: 17.0.0.Final)
(was: 18.0.0.Final)
(was: 19.0.0.Final)
(was: 20.0.0.Final)
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFCORE-5151
> URL: https://issues.redhat.com/browse/WFCORE-5151
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jan Stourac
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Darran Lofthouse reassigned WFLY-13935:
---------------------------------------
Assignee: (was: Darran Lofthouse)
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Jean Francois Denise reassigned WFLY-13935:
-------------------------------------------
Assignee: Darran Lofthouse (was: Jean Francois Denise)
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Assignee: Darran Lofthouse
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Jean Francois Denise updated WFLY-13935:
----------------------------------------
Component/s: Security
(was: CLI)
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Assignee: Jean Francois Denise
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13935:
---------------------------------------------
This issue is unrelated to CLI, the elytron subsystem handles attributes values.
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Assignee: Jean Francois Denise
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jan Stourac (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Jan Stourac updated WFLY-13935:
-------------------------------
Attachment: reproducer.sh
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Assignee: Jean Francois Denise
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months