January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2222) Only aggregate the wrapped realms if we really have something to aggregate.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2222: ---------------------------------------- Summary: Only aggregate the wrapped realms if we really have something to aggregate. Key: WFCORE-2222 URL: https://issues.jboss.org/browse/WFCORE-2222 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha20 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3884) Integrate mod_cluster subsystem with Elytron security subsystem for SSL configuration

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3884?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-3884: -------------------------------------- Integration branch: https://github.com/wildfly/wildfly/compare/master...rhusar:WFLY-3884v2?ex... > Integrate mod_cluster subsystem with Elytron security subsystem for SSL configuration > ------------------------------------------------------------------------------------- > > Key: WFLY-3884 > URL: https://issues.jboss.org/browse/WFLY-3884 > Project: WildFly > Issue Type: Feature Request > Components: mod_cluster > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 11.0.0.CR1 > > > Currently, the SSL certificate configuration is embedded within the mod_cluster subsystem configuration. Ideally, mod_cluster would reference this configuration from the security subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-675) OAuth2 Client Credentials CallbackHandler

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-675?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-675: --------------------------- Fix Version/s: 1.1.0.Beta18 > OAuth2 Client Credentials CallbackHandler > ----------------------------------------- > > Key: ELY-675 > URL: https://issues.jboss.org/browse/ELY-675 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Callbacks > Affects Versions: 1.1.0.Beta11 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta18 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-792) Allow security realms to associate a key with their realm identity instances

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-792?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-792: --------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/582, https://github.com/wildfly-security/wildfly-elytron/pull/591 (was: https://github.com/wildfly-security/wildfly-elytron/pull/582) > Allow security realms to associate a key with their realm identity instances > ---------------------------------------------------------------------------- > > Key: ELY-792 > URL: https://issues.jboss.org/browse/ELY-792 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI, Realms > Affects Versions: 1.1.0.Beta16 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta18 > > > * Kill off IL.principal completely > * Add RI.getKey which returns a key that is specific to the realm instance > * Add IL.key that, if present, is used to locate the identity; other fields in IL are checked against it and if there's a mismatch, an exception is thrown -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-792) Allow security realms to associate a key with their realm identity instances

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-792?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-792: --------------------------- Fix Version/s: 1.1.0.Beta18 > Allow security realms to associate a key with their realm identity instances > ---------------------------------------------------------------------------- > > Key: ELY-792 > URL: https://issues.jboss.org/browse/ELY-792 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI, Realms > Affects Versions: 1.1.0.Beta16 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta18 > > > * Kill off IL.principal completely > * Add RI.getKey which returns a key that is specific to the realm instance > * Add IL.key that, if present, is used to locate the identity; other fields in IL are checked against it and if there's a mismatch, an exception is thrown -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-886) Check for RealmIdentity.exists before caching

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-886?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-886: --------------------------- Fix Version/s: 1.1.0.Beta20 > Check for RealmIdentity.exists before caching > --------------------------------------------- > > Key: ELY-886 > URL: https://issues.jboss.org/browse/ELY-886 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta19 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta20 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-885) Make JDBC realm cacheable

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-885?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-885: --------------------------- Fix Version/s: 1.1.0.Beta20 > Make JDBC realm cacheable > ------------------------- > > Key: ELY-885 > URL: https://issues.jboss.org/browse/ELY-885 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Affects Versions: 1.1.0.Beta19 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta20 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-823) Constructor JaccDelegatingPolicy(Policy) not initializing supported permissions

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-823?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-823: --------------------------- Fix Version/s: 1.1.0.Beta18 (was: 1.1.0.Beta21) > Constructor JaccDelegatingPolicy(Policy) not initializing supported permissions > ------------------------------------------------------------------------------- > > Key: ELY-823 > URL: https://issues.jboss.org/browse/ELY-823 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Affects Versions: 1.1.0.Beta16 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta18 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-524) RealmIdentity data caching support in the LDAP realm

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-524?page=com.atlassian.jira.plugin.sy... ] Pedro Igor commented on ELY-524: -------------------------------- [~dmlloyd], I think we are ready to support these requirements. Right now, identities are already being cached but credential verification always demands a hit to the underlying LDAP store. I think we should be able now to load all credentials before returning an identity and have them cached. A similar behavior as we have for FS realm. > RealmIdentity data caching support in the LDAP realm > ---------------------------------------------------- > > Key: ELY-524 > URL: https://issues.jboss.org/browse/ELY-524 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Realms > Reporter: David Lloyd > Assignee: Pedro Igor > Priority: Critical > Fix For: 1.1.0.Beta21 > > > The LDAP realm should use a caching strategy to avoid excessive database load in the presence of per-request authentication traffic. > The realm implementation could maintain a synchronized LRU cache of one-time-initialize references to a cached DirContext or Attributes or binding or some combination of these. Because the cache is synchronized, the one-time-initialize object would be added under the lock and then the lock released before the object is populated and returned as a cached credential, allowing atomic action with a minimum of contention. > For each cached entity, a NamingListener could be established which would invalidate (or possibly update) the cached value as the database changes. > Alternatively, a NamingListener could be established for all identities, and each update would invalidate or update any cached values corresponding to the DN or resolved name. > This is a complex design topic so discussion is welcome. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7924) Value of parameter "restart-required" for configuration attributes does not match reality for datasource and resource adapter subsystems in CLI

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-7924?page=com.atlassian.jira.plugin.... ] Tomas Hofman moved JBEAP-8411 to WFLY-7924: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7924 (was: JBEAP-8411) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR7) (was: 7.1.0.DR8) > Value of parameter "restart-required" for configuration attributes does not match reality for datasource and resource adapter subsystems in CLI > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7924 > URL: https://issues.jboss.org/browse/WFLY-7924 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.1.0.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Original Estimate: 2 days > Remaining Estimate: 2 days > > All attributes of subsystems _datasources_ and _resource-adapters_ defines in its description that there is not necessary to do {{reload}} or {{restart}} for any of them. But reality is different. If you tries to change some of such attributes you are informed that reload is necessary. > All settable attributes are defined as > {code} > "restart-required" => "no-services" > {code} > Description of attributes should match reality of demands for {{reload}} being processed. > {quote} > * /subsystem=resource-adapters:read-resource-description(recursive=true) > * /subsystem=datasources:read-resource-description(recursive=true) > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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