April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-54) Add Keycloak authentication/authorization to http management endpoint

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-54?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFCORE-54: --------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Add Keycloak authentication/authorization to http management endpoint > --------------------------------------------------------------------- > > Key: WFCORE-54 > URL: https://issues.jboss.org/browse/WFCORE-54 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.0.0.CR1 > > > This is here to track the core changes needed for WFLY-3591. See that jira for details. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-43) Clarify the meaning of the 'server-state' and 'host-state' attributes

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-43?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFCORE-43: --------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Clarify the meaning of the 'server-state' and 'host-state' attributes > --------------------------------------------------------------------- > > Key: WFCORE-43 > URL: https://issues.jboss.org/browse/WFCORE-43 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 1.0.0.CR1 > > > This JIRA is to implement what I described in the dev list discussion around the various states a server can be in for graceful shutdown (http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002360.html) > "I do think these are orthogonal and should not be combined. > The existing attribute is fundamentally about how the state of the > runtime services relates to the persistent configuration. > STARTING == out of sync due to still getting in sync during start > RUNNING == in sync > RELOAD_REQURIRED = out of sync, needs a reload to get in sync > RESTART_REQUIRED = out of sync, needs a full process restart to get in sync > There are two problems though with the existing attribute that exposes this: > 1) It's named "server-state" on a server and "host-state" on a Host > Controller. Really crappy name; way too broad. > That's fixable by creating a new attribute and making the old one an > alias for compatibility purposes. > 2) The RUNNING state is really poorly named. > The could perhaps be fixed by coming up with a new name and translating > it back to "RUNNING" in the handlers for the legacy "server-state" and > "host-state" attributes." -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-109: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 1.0.0.CR1 > > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-107) Update whoami operation to return authentication mechanism where verbose=true

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-107?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-107: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > 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: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.CR1 > > > 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 (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-170) Create a shared ScheduledExecutorService

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-170?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-170: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Create a shared ScheduledExecutorService > ---------------------------------------- > > Key: WFCORE-170 > URL: https://issues.jboss.org/browse/WFCORE-170 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.CR1 > > > There are number of ScheduledExecutorService instances being created around wf-core. Create a single service and inject it. > This will reduce resource usage by creating fewer threads, and will reduce the risk of code mistakes around shutting down the various executors, > I see these used in: > LdapCacheService > RemoteDomainConnectionService > DeploymentMountProvider > DeploymentScannerService > plus the operation response attachment stuff I'm doing will need one. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-137) Add Kerberos tests to domain-management module

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-137?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-137: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Add Kerberos tests to domain-management module > ---------------------------------------------- > > Key: WFCORE-137 > URL: https://issues.jboss.org/browse/WFCORE-137 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-129: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.CR1 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-114) Get RuntimeVaultReader into WildFly Core

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-114?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-114: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Get RuntimeVaultReader into WildFly Core > ---------------------------------------- > > Key: WFCORE-114 > URL: https://issues.jboss.org/browse/WFCORE-114 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Priority: Blocker > Fix For: 1.0.0.CR1 > > > The only real implementation of AbstractVaultReader isn't in wildfly-core; it's in the wildfly-full security subsystem module. > This means WildFly Core currently doesn't really support vault expressions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-287) Provide an operation to execute domain wide queries on the server side

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-287?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-287: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Provide an operation to execute domain wide queries on the server side > ---------------------------------------------------------------------- > > Key: WFCORE-287 > URL: https://issues.jboss.org/browse/WFCORE-287 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 1.0.0.CR1 > > > i.e. retrieve all 'enabled' datasources that use the 'h2' driver: > {code:java} > ModelNode address = new ModelNode(); > address.add("profile", "*") > .add("subsystem", "datasources") > .add("data-source", "*"); > ModelNode filter = new ModelNode(); > filter.add("driver-name", "h2") > .add("enabled", true); > ModelNode op = new ModelNode(); > op.get(OP).set(QUERY); > op.get(ADDRESS).set(address); > op.get(WHERE).set(filter); > {code} > Another example using the CLI: > {code} > [standalone@localhost:9990 /] /path=*:query(select=[path], where={name="jboss.home.dir"}) > { > "outcome" => "success", > "result" => [{ > "address" => [("path" => "jboss.home.dir")], > "outcome" => "success", > "result" => {"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT"} > }] > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-282) Wildcard operations that span multiple processes

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-282?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-282: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Wildcard operations that span multiple processes > ------------------------------------------------ > > Key: WFCORE-282 > URL: https://issues.jboss.org/browse/WFCORE-282 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: as7-ignored > Fix For: 1.0.0.CR1 > > > Handle host=* and host=y,server=* type operations. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015