February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1402) Add support for metaspacesize to jvm options and remove permgen

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-1402: ------------------------------ Description: This change should allow the configured jvm metaspace to be displayed as an attribute under /host=/jvm and /host=/server-config/jvm. The value should not be persisted, and would probably just be parsed out of the jvm startup options -XX:MetaspaceSize= and -XX:MetaspaceMaxSize= (was: We could display the configured Metaspace values, and we should remove the now deprecated permgen values.) > Add support for metaspacesize to jvm options and remove permgen > --------------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > This change should allow the configured jvm metaspace to be displayed as an attribute under /host=/jvm and /host=/server-config/jvm. The value should not be persisted, and would probably just be parsed out of the jvm startup options -XX:MetaspaceSize= and -XX:MetaspaceMaxSize= -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1402) Add support for metaspacesize to jvm options and remove permgen

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1402?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-1402: ----------------------------------- Thanks for the clarification, I thought we'd be treating it like permgen going forward. So based on that, we'd either just want to leave it available in its generic form under jvm-options, or we could parse it out for display. Do you think there's any value in that? If not, I'll close this an file under "mistake." :) > Add support for metaspacesize to jvm options and remove permgen > --------------------------------------------------------------- > > Key: WFCORE-1402 > URL: https://issues.jboss.org/browse/WFCORE-1402 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > We could display the configured Metaspace values, and we should remove the now deprecated permgen values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-421) IBM JDK uses a slightly different stack for property permission checking

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-421?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-421: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.Beta4) (was: 1.0.3.CR1) > IBM JDK uses a slightly different stack for property permission checking > ------------------------------------------------------------------------ > > Key: ELY-421 > URL: https://issues.jboss.org/browse/ELY-421 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta5 > > > On some IBM JDKs, System.getProperty delegates to other System methods. The security manager does not account for that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-263) Revisit ServerAuthenticationContext.querySaslServerMechanismNames

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-263?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-263: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.Beta4) > Revisit ServerAuthenticationContext.querySaslServerMechanismNames > ----------------------------------------------------------------- > > Key: ELY-263 > URL: https://issues.jboss.org/browse/ELY-263 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > Does this method still have a use? > If so we probably need to adjust all filtering factory implements to support the query all flag. > Also if it does HTTP may need the same treatment. > If not maybe we remove the whole method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-401) ELY01077: Invalid alias "TLS_RSA_WITH_DES_CBC_SHA" for missing mechanism database entry "TLS_RSA_FIPS_WITH_DES_CBC_SHA"

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-401?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-401: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.Beta4) > ELY01077: Invalid alias "TLS_RSA_WITH_DES_CBC_SHA" for missing mechanism database entry "TLS_RSA_FIPS_WITH_DES_CBC_SHA" > ----------------------------------------------------------------------------------------------------------------------- > > Key: ELY-401 > URL: https://issues.jboss.org/browse/ELY-401 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL, Utils > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > Getting the following warning logged when filtering the ciphers available from Oracle Java 8 with unlimited strength policy files in place: - > {noformat} > ELY01077: Invalid alias "TLS_RSA_WITH_DES_CBC_SHA" for missing mechanism database entry "TLS_RSA_FIPS_WITH_DES_CBC_SHA" > {noformat} > _The JCE policy is probably unrelated, mentioning it just in case._ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-344) Review how clients use ModifiableRealmIdentity / ModifiableRealm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-344?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-344: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.Beta4) > Review how clients use ModifiableRealmIdentity / ModifiableRealm > ---------------------------------------------------------------- > > Key: ELY-344 > URL: https://issues.jboss.org/browse/ELY-344 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > This may be something we address in the subsystem but just raising here so we don't forget. > Once we have a working set up with a realm which can be modified it seems unreasonable to expect the administrator to know exactly which credential types and names to use. > This may need to be a few milestones away once we have the bulk integrated so the relationships are clear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-107) Add ability for security domains to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-107?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-107: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.Beta4) > Add ability for security domains to create SSLContext directly from config > -------------------------------------------------------------------------- > > Key: ELY-107 > URL: https://issues.jboss.org/browse/ELY-107 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: Darran Lofthouse > Labels: elytron_ssl > Fix For: 1.1.0.Beta5 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-298) load-from/uri keystore xsd/parser mismatch

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-298?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-298: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.Beta4) > load-from/uri keystore xsd/parser mismatch > ------------------------------------------ > > Key: ELY-298 > URL: https://issues.jboss.org/browse/ELY-298 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > The xsd has > {code} > <xsd:complexType name="key-store-type"> > <xsd:sequence minOccurs="1" maxOccurs="1"> >  > <xsd:choice minOccurs="1" maxOccurs="1"> > <xsd:element name="file" type="name-type" minOccurs="1" maxOccurs="1"/> > <xsd:element name="load-from" type="uri-type" minOccurs="1" maxOccurs="1"/> > <xsd:element name="resource" type="name-type" minOccurs="1" maxOccurs="1"/> > {code} > The parser seems to look for 'uri' rather than 'load-from' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-211) Client-side trust store configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-211?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-211: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.Beta4) > Client-side trust store configuration > ------------------------------------- > > Key: ELY-211 > URL: https://issues.jboss.org/browse/ELY-211 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta5 > > > Lest I forget. The client needs the ability to supplement the default trust store, to restrict the set of acceptable peer certificates/signers, for mutual authentication purposes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-279) Support CORS

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-279?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-279: --------------------------------- Fix Version/s: 1.1.0.Beta5 (was: 1.1.0.Beta4) > Support CORS > ------------ > > Key: ELY-279 > URL: https://issues.jboss.org/browse/ELY-279 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > This is something that can possibly be tied in around the HTTP authentication framework meaning that the control of this can live in the HTTP authentication policy within Elytron rather than at the front end. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 February 2016