January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-6) [QE] - JMAN4-159 - OpenShift EAP 7 Docker image with Hawkular Agent

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-6: --------------------------------------- Summary: [QE] - JMAN4-159 - OpenShift EAP 7 Docker image with Hawkular Agent Key: HAWKULARQE-6 URL: https://issues.jboss.org/browse/HAWKULARQE-6 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: mfoley user Priority: Blocker See [JMAN4-159|https://issues.jboss.org/browse/JMAN4-159] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-6) [QE] - JMAN4-159 - OpenShift EAP 7 Docker image with Hawkular Agent

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-6?page=com.atlassian.jira.plug... ] Hayk Hovsepyan updated HAWKULARQE-6: ------------------------------------ Labels: mm-integration-hawkular-qe (was: ) > [QE] - JMAN4-159 - OpenShift EAP 7 Docker image with Hawkular Agent > ------------------------------------------------------------------- > > Key: HAWKULARQE-6 > URL: https://issues.jboss.org/browse/HAWKULARQE-6 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: mfoley user > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-159|https://issues.jboss.org/browse/JMAN4-159] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-2) [QE] - JMAN4-112 - Cross-Link JBoss Middleware services to containers

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-2?page=com.atlassian.jira.plug... ] Hayk Hovsepyan updated HAWKULARQE-2: ------------------------------------ Summary: [QE] - JMAN4-112 - Cross-Link JBoss Middleware services to containers (was: [QE] Cross-Link JBoss Middleware services to containers) > [QE] - JMAN4-112 - Cross-Link JBoss Middleware services to containers > --------------------------------------------------------------------- > > Key: HAWKULARQE-2 > URL: https://issues.jboss.org/browse/HAWKULARQE-2 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: mfoley user > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-112|https://issues.jboss.org/browse/JMAN4-112] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-1) [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-1?page=com.atlassian.jira.plug... ] Hayk Hovsepyan updated HAWKULARQE-1: ------------------------------------ Summary: [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers (was: [QE] Immutability of JBoss Middleware services running in containers) > [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers > ---------------------------------------------------------------------------------- > > Key: HAWKULARQE-1 > URL: https://issues.jboss.org/browse/HAWKULARQE-1 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: mfoley user > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-111|https://issues.jboss.org/browse/JMAN4-111] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-835) SecurityIdentity Automatic Outflow

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-835?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-835: ------------------------------------ Assignee: Darran Lofthouse (was: Jan Kalina) > SecurityIdentity Automatic Outflow > ---------------------------------- > > Key: ELY-835 > URL: https://issues.jboss.org/browse/ELY-835 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta22 > > > We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains (which it has in trusted-security-domains?) so it does not need to be manually inflowed at a later point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8001) System property wildfly.config.url doesn't resolve correctly relative paths

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8001: --------------------------------- Summary: System property wildfly.config.url doesn't resolve correctly relative paths Key: WFLY-8001 URL: https://issues.jboss.org/browse/WFLY-8001 Project: WildFly Issue Type: Bug Components: Security Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Critical When an AS client runs with custom Elytron configuration specified and system property {{wildfly.config.url}} is used to provide the configuration (as a relative path), then the resolved URI is not correct. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2246) Undertow 1.4.9.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-2246: -------------------------------------- Summary: Undertow 1.4.9.Final Key: WFCORE-2246 URL: https://issues.jboss.org/browse/WFCORE-2246 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2247) Undertow 1.4.9.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-2247: -------------------------------------- Summary: Undertow 1.4.9.Final Key: WFCORE-2247 URL: https://issues.jboss.org/browse/WFCORE-2247 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8000) Default Elytron realm names are confusing - use same values as Legacy security realms

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8000?page=com.atlassian.jira.plugin.... ] Josef Cacek updated WFLY-8000: ------------------------------ Labels: user_experience (was: ) > Default Elytron realm names are confusing - use same values as Legacy security realms > ------------------------------------------------------------------------------------- > > Key: WFLY-8000 > URL: https://issues.jboss.org/browse/WFLY-8000 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Priority: Blocker > Labels: user_experience > > The default application server profiles now contain Elytron subsystem configured (more in EAP7-543). The subsystem contains 2 properties realms, which copy behavior of security realms in legacy security. They use the same name as the original ones *ApplicationRealm* and *ManagementRealm*: > {code:xml} > <properties-realm name="ApplicationRealm"> > <users-properties path="application-users.properties" relative-to="jboss.server.config.dir" digest-realm-name="ApplicationRealm"/> > <groups-properties path="application-roles.properties" relative-to="jboss.server.config.dir"/> > </properties-realm> > <properties-realm name="ManagementRealm"> > <users-properties path="mgmt-users.properties" relative-to="jboss.server.config.dir" digest-realm-name="ManagementRealm"/> > <groups-properties path="mgmt-groups.properties" relative-to="jboss.server.config.dir"/> > </properties-realm> > {code} > The new Elytron realms must use different names than legacy ones. Otherwise customers/administrators may think about the Elytron realms as just references to the legacy security. > *Suggested solution* > Rename the default Elytron realms to something like *ElytronManagementRealm* or *ManagementElytronRealm*. So the configuration looks like: > {code:xml} > <properties-realm name="ApplicationElytronRealm"> > <users-properties path="application-users.properties" relative-to="jboss.server.config.dir" digest-realm-name="ApplicationRealm"/> > <groups-properties path="application-roles.properties" relative-to="jboss.server.config.dir"/> > </properties-realm> > <properties-realm name="ManagementElytronRealm"> > <users-properties path="mgmt-users.properties" relative-to="jboss.server.config.dir" digest-realm-name="ManagementRealm"/> > <groups-properties path="mgmt-groups.properties" relative-to="jboss.server.config.dir"/> > </properties-realm> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8000) Default Elytron realm names are confusing - use same values as Legacy security realms

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8000: --------------------------------- Summary: Default Elytron realm names are confusing - use same values as Legacy security realms Key: WFLY-8000 URL: https://issues.jboss.org/browse/WFLY-8000 Project: WildFly Issue Type: Bug Components: Security Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Blocker The default application server profiles now contain Elytron subsystem configured (more in EAP7-543). The subsystem contains 2 properties realms, which copy behavior of security realms in legacy security. They use the same name as the original ones *ApplicationRealm* and *ManagementRealm*: {code:xml} <properties-realm name="ApplicationRealm"> <users-properties path="application-users.properties" relative-to="jboss.server.config.dir" digest-realm-name="ApplicationRealm"/> <groups-properties path="application-roles.properties" relative-to="jboss.server.config.dir"/> </properties-realm> <properties-realm name="ManagementRealm"> <users-properties path="mgmt-users.properties" relative-to="jboss.server.config.dir" digest-realm-name="ManagementRealm"/> <groups-properties path="mgmt-groups.properties" relative-to="jboss.server.config.dir"/> </properties-realm> {code} The new Elytron realms must use different names than legacy ones. Otherwise customers/administrators may think about the Elytron realms as just references to the legacy security. *Suggested solution* Rename the default Elytron realms to something like *ElytronManagementRealm* or *ManagementElytronRealm*. So the configuration looks like: {code:xml} <properties-realm name="ApplicationElytronRealm"> <users-properties path="application-users.properties" relative-to="jboss.server.config.dir" digest-realm-name="ApplicationRealm"/> <groups-properties path="application-roles.properties" relative-to="jboss.server.config.dir"/> </properties-realm> <properties-realm name="ManagementElytronRealm"> <users-properties path="mgmt-users.properties" relative-to="jboss.server.config.dir" digest-realm-name="ManagementRealm"/> <groups-properties path="mgmt-groups.properties" relative-to="jboss.server.config.dir"/> </properties-realm> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017