[JBoss JIRA] (WFCORE-2884) Create test cases for Elytron custom-* resources
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2884?page=com.atlassian.jira.plugi... ]
Kabir Khan moved WFLY-8834 to WFCORE-2884:
------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2884 (was: WFLY-8834)
Component/s: Test Suite
(was: Test Suite)
> Create test cases for Elytron custom-* resources
> ------------------------------------------------
>
> Key: WFCORE-2884
> URL: https://issues.jboss.org/browse/WFCORE-2884
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Reporter: Hynek Švábek
> Assignee: Hynek Švábek
>
> Create test cases for following Elytron custom-* resources:
> * custom-modifiable-realm
> * custom-permission-mapper
> * custom-principal-decoder
> * custom-principal-transformer
> * custom-realm
> * custom-realm-mapper
> * custom-role-decoder
> * custom-role-mapper
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (DROOLS-1583) Refactor KnowledgeBaseImpl
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1583?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-1583:
--------------------------------
Sprint: Sprint 5
> Refactor KnowledgeBaseImpl
> --------------------------
>
> Key: DROOLS-1583
> URL: https://issues.jboss.org/browse/DROOLS-1583
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Matteo Mortari
>
> It is required to review the KnowledgeBaseImpl and lower the technical debt accumulated on it by:
> # Remove unnecessary duplicated methods that at the moment are there only for backward compatibility reasons.
> # Review the locks and in particular check if some of them can be removed since now the kbase changes are enqueued.
> # Review the rules/packages addition lifecycle emitting events before and after them (and in general reviewing the existing events).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (DROOLS-1583) Refactor KnowledgeBaseImpl
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1583?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-1583:
-----------------------------------
Assignee: Mario Fusco (was: Matteo Mortari)
> Refactor KnowledgeBaseImpl
> --------------------------
>
> Key: DROOLS-1583
> URL: https://issues.jboss.org/browse/DROOLS-1583
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> It is required to review the KnowledgeBaseImpl and lower the technical debt accumulated on it by:
> # Remove unnecessary duplicated methods that at the moment are there only for backward compatibility reasons.
> # Review the locks and in particular check if some of them can be removed since now the kbase changes are enqueued.
> # Review the rules/packages addition lifecycle emitting events before and after them (and in general reviewing the existing events).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (DROOLS-1583) Refactor KnowledgeBaseImpl
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1583?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-1583:
-----------------------------------
Assignee: Matteo Mortari (was: Mario Fusco)
> Refactor KnowledgeBaseImpl
> --------------------------
>
> Key: DROOLS-1583
> URL: https://issues.jboss.org/browse/DROOLS-1583
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Matteo Mortari
>
> It is required to review the KnowledgeBaseImpl and lower the technical debt accumulated on it by:
> # Remove unnecessary duplicated methods that at the moment are there only for backward compatibility reasons.
> # Review the locks and in particular check if some of them can be removed since now the kbase changes are enqueued.
> # Review the rules/packages addition lifecycle emitting events before and after them (and in general reviewing the existing events).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (DROOLS-1583) Refactor KnowledgeBaseImpl
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1583?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-1583:
-----------------------------------
Assignee: Matteo Mortari (was: Mario Fusco)
> Refactor KnowledgeBaseImpl
> --------------------------
>
> Key: DROOLS-1583
> URL: https://issues.jboss.org/browse/DROOLS-1583
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Matteo Mortari
>
> It is required to review the KnowledgeBaseImpl and lower the technical debt accumulated on it by:
> # Remove unnecessary duplicated methods that at the moment are there only for backward compatibility reasons.
> # Review the locks and in particular check if some of them can be removed since now the kbase changes are enqueued.
> # Review the rules/packages addition lifecycle emitting events before and after them (and in general reviewing the existing events).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ELY-1208) Elytron dir-context ignores protocol, host and port options from Authentication Configuration
by Ondrej Lukas (JIRA)
Ondrej Lukas created ELY-1208:
---------------------------------
Summary: Elytron dir-context ignores protocol, host and port options from Authentication Configuration
Key: ELY-1208
URL: https://issues.jboss.org/browse/ELY-1208
Project: WildFly Elytron
Issue Type: Bug
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Blocker
When Elytron {{dir-context}} uses {{authentication-context}} and obtains some authentication configuration from it then dir context ignores obtained protocol, host and port options from authentication configuration. Original {{dir-context.url}} is used without any change.
It means some authentication client like following cannot be used with dir context:
{code}
<authentication-client>
<authentication-configuration name="unsecureConfig" authentication-name="uid=admin,ou=system">
<credential-reference clear-text="secret"/>
</authentication-configuration>
<authentication-configuration name="secureConfig" authentication-name="uid=admin,ou=system" protocol="ldaps" port="10636">
<credential-reference clear-text="secret"/>
</authentication-configuration>
<authentication-context name="authCtx">
<match-rule match-purpose="secure" authentication-configuration="secureConfig"/>
<match-rule authentication-configuration="unsecureConfig"/>
</authentication-context>
</authentication-client>
...
<dir-contexts>
<dir-context name="dir-context" url="ldap://127.0.0.1:10389" authentication-context="authCtx"/>
</dir-contexts>
{code}
We request blocker since {{dir-context}} is not able to use feature which are provided by {{authentication-context}} which means lack of features for {{dir-context}} and can be confused for users.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ELY-1208) Elytron dir-context ignores protocol, host and port options from Authentication Configuration
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1208?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1208:
------------------------------
Description:
When Elytron {{dir-context}} uses {{authentication-context}} and obtains some authentication configuration from it then dir context ignores obtained protocol, host and port options from authentication configuration. Original {{dir-context.url}} is used without any change.
It means some authentication client like following cannot be used with dir context:
{code}
<authentication-client>
<authentication-configuration name="unsecureConfig" authentication-name="uid=admin,ou=system">
<credential-reference clear-text="secret"/>
</authentication-configuration>
<authentication-configuration name="secureConfig" authentication-name="uid=admin,ou=system" protocol="ldaps" port="10636">
<credential-reference clear-text="secret"/>
</authentication-configuration>
<authentication-context name="authCtx">
<match-rule match-purpose="secure" authentication-configuration="secureConfig"/>
<match-rule authentication-configuration="unsecureConfig"/>
</authentication-context>
</authentication-client>
...
<dir-contexts>
<dir-context name="dir-context" url="ldap://127.0.0.1:10389" authentication-context="authCtx"/>
</dir-contexts>
{code}
was:
When Elytron {{dir-context}} uses {{authentication-context}} and obtains some authentication configuration from it then dir context ignores obtained protocol, host and port options from authentication configuration. Original {{dir-context.url}} is used without any change.
It means some authentication client like following cannot be used with dir context:
{code}
<authentication-client>
<authentication-configuration name="unsecureConfig" authentication-name="uid=admin,ou=system">
<credential-reference clear-text="secret"/>
</authentication-configuration>
<authentication-configuration name="secureConfig" authentication-name="uid=admin,ou=system" protocol="ldaps" port="10636">
<credential-reference clear-text="secret"/>
</authentication-configuration>
<authentication-context name="authCtx">
<match-rule match-purpose="secure" authentication-configuration="secureConfig"/>
<match-rule authentication-configuration="unsecureConfig"/>
</authentication-context>
</authentication-client>
...
<dir-contexts>
<dir-context name="dir-context" url="ldap://127.0.0.1:10389" authentication-context="authCtx"/>
</dir-contexts>
{code}
We request blocker since {{dir-context}} is not able to use feature which are provided by {{authentication-context}} which means lack of features for {{dir-context}} and can be confused for users.
> Elytron dir-context ignores protocol, host and port options from Authentication Configuration
> ---------------------------------------------------------------------------------------------
>
> Key: ELY-1208
> URL: https://issues.jboss.org/browse/ELY-1208
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta47
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> When Elytron {{dir-context}} uses {{authentication-context}} and obtains some authentication configuration from it then dir context ignores obtained protocol, host and port options from authentication configuration. Original {{dir-context.url}} is used without any change.
> It means some authentication client like following cannot be used with dir context:
> {code}
> <authentication-client>
> <authentication-configuration name="unsecureConfig" authentication-name="uid=admin,ou=system">
> <credential-reference clear-text="secret"/>
> </authentication-configuration>
> <authentication-configuration name="secureConfig" authentication-name="uid=admin,ou=system" protocol="ldaps" port="10636">
> <credential-reference clear-text="secret"/>
> </authentication-configuration>
> <authentication-context name="authCtx">
> <match-rule match-purpose="secure" authentication-configuration="secureConfig"/>
> <match-rule authentication-configuration="unsecureConfig"/>
> </authentication-context>
> </authentication-client>
> ...
> <dir-contexts>
> <dir-context name="dir-context" url="ldap://127.0.0.1:10389" authentication-context="authCtx"/>
> </dir-contexts>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ELY-1208) Elytron dir-context ignores protocol, host and port options from Authentication Configuration
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1208?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1208:
------------------------------
Affects Version/s: 1.1.0.Beta47
> Elytron dir-context ignores protocol, host and port options from Authentication Configuration
> ---------------------------------------------------------------------------------------------
>
> Key: ELY-1208
> URL: https://issues.jboss.org/browse/ELY-1208
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta47
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> When Elytron {{dir-context}} uses {{authentication-context}} and obtains some authentication configuration from it then dir context ignores obtained protocol, host and port options from authentication configuration. Original {{dir-context.url}} is used without any change.
> It means some authentication client like following cannot be used with dir context:
> {code}
> <authentication-client>
> <authentication-configuration name="unsecureConfig" authentication-name="uid=admin,ou=system">
> <credential-reference clear-text="secret"/>
> </authentication-configuration>
> <authentication-configuration name="secureConfig" authentication-name="uid=admin,ou=system" protocol="ldaps" port="10636">
> <credential-reference clear-text="secret"/>
> </authentication-configuration>
> <authentication-context name="authCtx">
> <match-rule match-purpose="secure" authentication-configuration="secureConfig"/>
> <match-rule authentication-configuration="unsecureConfig"/>
> </authentication-context>
> </authentication-client>
> ...
> <dir-contexts>
> <dir-context name="dir-context" url="ldap://127.0.0.1:10389" authentication-context="authCtx"/>
> </dir-contexts>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months