[JBoss JIRA] (WFCORE-107) Update whoami operation to return authentication mechanism where verbose=true
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-107?page=com.atlassian.jira.plugin... ]
Darran Lofthouse resolved WFCORE-107.
-------------------------------------
Resolution: Won't Do
No demand for this change.
> Update whoami operation to return authentication mechanism where verbose=true
> -----------------------------------------------------------------------------
>
> Key: WFCORE-107
> URL: https://issues.jboss.org/browse/WFCORE-107
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
>
> The admin console currently contains a "logout" handler that follows a round of HTTP message exchanges to trick the web browser into forgetting the credentials it has cached.
> This only makes sense where the browser has cached a credential - if we return the authentication mechanism then the console can make a better decision regarding displaying the logout link or could change the implementation so display a message to the user explaining why logout does not make sense.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-1145) Review of HostController / Application Server Remoting connections
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-1145?page=com.atlassian.jira.plugi... ]
Darran Lofthouse resolved WFCORE-1145.
--------------------------------------
Resolution: Out of Date
> Review of HostController / Application Server Remoting connections
> ------------------------------------------------------------------
>
> Key: WFCORE-1145
> URL: https://issues.jboss.org/browse/WFCORE-1145
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Labels: affects_elytron, domain-mode
>
> Where an application server connects back to it's host controller in domain mode it used the same Remoting connector exposed possibly for native domain management access.
> The problem with this is that as soon as any security restrictions are placed on the connector exposed by the host controller then the application servers require something to work with this - this is even though we are only ever talking about loopback communication between two process on the same machine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-2346) Revisit enforcement of required file system permissions.
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-2346?page=com.atlassian.jira.plugi... ]
Darran Lofthouse resolved WFCORE-2346.
--------------------------------------
Resolution: Out of Date
> Revisit enforcement of required file system permissions.
> --------------------------------------------------------
>
> Key: WFCORE-2346
> URL: https://issues.jboss.org/browse/WFCORE-2346
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Labels: management_security,
>
> Now that AS8 has moved to Java 7 we can re-visit the level of control we have over file system permissions, this can be from taking more control of the local authentication mechanism to ensure incorrect permissions are not inherited to verifying sensitive configuration files are not world readable.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11530) Distributed @Stateful EJB implementation should not hold references to CapabilityServiceSupport
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-11530:
-----------------------------------
Summary: Distributed @Stateful EJB implementation should not hold references to CapabilityServiceSupport
Key: WFLY-11530
URL: https://issues.jboss.org/browse/WFLY-11530
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 15.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
The Distributed @Stateful EJB implementation currently holds references to the CapabilityServiceSupport obtained via the OperationContext, in order to resolve capability names. We should migrate this code to fully leverage CapabilityServiceConfigurator when configuring service dependencies.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-1781) Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-1781?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1781:
-------------------------------------
Description:
SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
*How to migrate*
* Replace
{code}
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
{code}
by
{code}
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
{code}
* Look for all "findbugs" and replace it by "spotbugs"
** Except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave that one alone!
** For example, change findbugs-check -> spotbugs-check, ...
* Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
* Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
** Ignore contributed experiments, that repo is dead
was:
SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
*How to migrate*
* Replace
{code}
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
{code}
by
{code}
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
{code}
* Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
** findbugs-check -> spotbugs-check
** ...
* Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
* Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
** Ignore contributed experiments, that repo is dead
> Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-1781
> URL: https://issues.jboss.org/browse/DROOLS-1781
> Project: Drools
> Issue Type: Task
> Components: build
> Affects Versions: 7.4.1.Final
> Reporter: Petr Široký
> Priority: Major
> Labels: java9
>
> SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
> *How to migrate*
> * Replace
> {code}
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> {code}
> by
> {code}
> <groupId>com.github.spotbugs</groupId>
> <artifactId>spotbugs-maven-plugin</artifactId>
> {code}
> * Look for all "findbugs" and replace it by "spotbugs"
> ** Except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave that one alone!
> ** For example, change findbugs-check -> spotbugs-check, ...
> * Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
> * Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
> ** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
> ** Ignore contributed experiments, that repo is dead
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-1781) Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-1781?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1781:
-------------------------------------
Description:
SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
*How to migrate*
* Replace
{code}
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
{code}
by
{code}
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
{code}
* Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
** findbugs-check -> spotbugs-check
** ...
* Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
* Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
** Ignore contributed experiments, that repo is dead
was:
SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
*How to migrate*
* Replace
{code}
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
{code}
by
{code}
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
{code}
* * Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
** findbugs-check -> spotbugs-check
** ...
* Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
* Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
** Ignore contributed experiments, that repo is dead
> Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-1781
> URL: https://issues.jboss.org/browse/DROOLS-1781
> Project: Drools
> Issue Type: Task
> Components: build
> Affects Versions: 7.4.1.Final
> Reporter: Petr Široký
> Priority: Major
> Labels: java9
>
> SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
> *How to migrate*
> * Replace
> {code}
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> {code}
> by
> {code}
> <groupId>com.github.spotbugs</groupId>
> <artifactId>spotbugs-maven-plugin</artifactId>
> {code}
> * Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
> ** findbugs-check -> spotbugs-check
> ** ...
> * Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
> * Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
> ** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
> ** Ignore contributed experiments, that repo is dead
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-1781) Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-1781?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1781:
-------------------------------------
Description:
SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
*How to migrate*
* Replace
{code}
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
{code}
by
{code}
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
{code}
* * Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
** findbugs-check -> spotbugs-check
** ...
* Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
* Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
** Ignore contributed experiments, that repo is dead
was:
SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
*How to migrate (by Geoffrey)*
* Replace
{code}
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
{code}
by
{code}
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
{code}
* * Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
** findbugs-check -> spotbugs-check
** ...
* Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
* Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
** Ignore contributed experiments, that repo is dead
> Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-1781
> URL: https://issues.jboss.org/browse/DROOLS-1781
> Project: Drools
> Issue Type: Task
> Components: build
> Affects Versions: 7.4.1.Final
> Reporter: Petr Široký
> Priority: Major
> Labels: java9
>
> SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
> *How to migrate*
> * Replace
> {code}
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> {code}
> by
> {code}
> <groupId>com.github.spotbugs</groupId>
> <artifactId>spotbugs-maven-plugin</artifactId>
> {code}
> * * Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
> ** findbugs-check -> spotbugs-check
> ** ...
> * Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
> * Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
> ** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
> ** Ignore contributed experiments, that repo is dead
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-1781) Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-1781?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1781:
-------------------------------------
Description:
SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
*How to migrate (by Geoffrey)*
* Replace
{code}
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
{code}
by
{code}
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
{code}
* * Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
** findbugs-check -> spotbugs-check
** ...
* Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
* Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
** Ignore contributed experiments, that repo is dead
was:SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
> Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-1781
> URL: https://issues.jboss.org/browse/DROOLS-1781
> Project: Drools
> Issue Type: Task
> Components: build
> Affects Versions: 7.4.1.Final
> Reporter: Petr Široký
> Priority: Major
> Labels: java9
>
> SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible.
> *How to migrate (by Geoffrey)*
> * Replace
> {code}
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>findbugs-maven-plugin</artifactId>
> {code}
> by
> {code}
> <groupId>com.github.spotbugs</groupId>
> <artifactId>spotbugs-maven-plugin</artifactId>
> {code}
> * * Look for all "findbugs" and replace it by "spotbugs", except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave those alone.
> ** findbugs-check -> spotbugs-check
> ** ...
> * Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320
> * Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions.
> ** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code
> ** Ignore contributed experiments, that repo is dead
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months