August 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-587) SSLContext integration into DirContext supplier service

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-587?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-587 at 8/25/16 2:05 PM: --------------------------------------------------------- *In the end ThreadLocal variable is used.* I was worry about possible auto-reconnect inside of DirContext - as the ThreadLocal variable is set only during DirContext construction/reconnect() method call, auto-reconnect after TCP connection breaking would fail - variable would not be set and would not be posible to determine for which DirContext should be SSLSocketFactory provided. *This risk was disproved* by experiment - standard DirContext doesnt reconnect interrupted TCP connections - it throws *CommunicationException: connection closed* exception instead. (which is OK) was (Author: honza889): In the end ThreadLocal variable is used. I was worry about possible auto-reconnect inside of DirContext - as the ThreadLocal variable is set only during DirContext construction/reconnect() method call, auto-reconnect after TCP connection breaking would fail - variable would not be set and would not be posible to determine for which DirContext should be SSLSocketFactory provided. *This risk was disproved* by experiment - standard DirContext doesnt reconnect interrupted TCP connections - it throws *CommunicationException: connection closed* exception instead. (which is OK) > SSLContext integration into DirContext supplier service > ------------------------------------------------------- > > Key: ELY-587 > URL: https://issues.jboss.org/browse/ELY-587 > Project: WildFly Elytron > Issue Type: Task > Components: SSL > Reporter: Jan Kalina > Assignee: Jan Kalina > > * we already have a resource to define the SSLContext > * we want use it for connection to LDAP > * resource of DirContext supplier (see ELY-462) should reference SSLContext resource / capability -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7012) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7012?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7012: -------------------------------------- Description: The contract for this capability needs examination and recording in the registry. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. was: The contract for this capability needs examination and recording in the registry. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. Assignee: Stuart Douglas (was: Ingo Weiss) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7012 > URL: https://issues.jboss.org/browse/WFLY-7012 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Stuart Douglas > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7011) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7011?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7011: -------------------------------------- Assignee: Ingo Weiss (was: Brian Stansberry) [~iweiss] I'm assigning this to you as a follow up to our chat today. This is one of various JIRAs I'm opening as I examine the state of https://github.com/wildfly/wildfly-capabilities compared to the WildFly [Core] code. [~swd847] FYI. > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-7011 > URL: https://issues.jboss.org/browse/WFLY-7011 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Ingo Weiss > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7012) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7012: -------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler Key: WFLY-7012 URL: https://issues.jboss.org/browse/WFLY-7012 Project: WildFly Issue Type: Bug Components: Security Reporter: Brian Stansberry Assignee: Ingo Weiss The contract for this capability needs examination and recording in the registry. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7011) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7011?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7011: ----------------------------------- Description: The contract for this capability needs examination and recording in the registry. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. was: This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-7011 > URL: https://issues.jboss.org/browse/WFLY-7011 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7011) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7011: -------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener Key: WFLY-7011 URL: https://issues.jboss.org/browse/WFLY-7011 Project: WildFly Issue Type: Bug Components: Security Reporter: Brian Stansberry Assignee: Brian Stansberry This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7010) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.transactions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7010?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7010: ----------------------------------- Description: This cap was introduced to support an optional requirement by the security subsystem for transaction manager integration. Both sides of this contract need examination. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. was:This cap was introduced to support an optional requirement by the security subsystem for transaction manager integration. Both sides of this contract need examination. > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.transactions > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-7010 > URL: https://issues.jboss.org/browse/WFLY-7010 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > This cap was introduced to support an optional requirement by the security subsystem for transaction manager integration. Both sides of this contract need examination. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7009) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.security

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7009?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7009: ----------------------------------- Description: This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. was:This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.security > ------------------------------------------------------------------------------------------------- > > Key: WFLY-7009 > URL: https://issues.jboss.org/browse/WFLY-7009 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7010) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.transactions

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7010: -------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.transactions Key: WFLY-7010 URL: https://issues.jboss.org/browse/WFLY-7010 Project: WildFly Issue Type: Bug Components: Security Reporter: Brian Stansberry Assignee: Brian Stansberry This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7010) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.transactions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7010?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7010: ----------------------------------- Component/s: Transactions (was: Security) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.transactions > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-7010 > URL: https://issues.jboss.org/browse/WFLY-7010 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 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 August 2016