[JBoss JIRA] (SECURITY-971) SecurityKeyManager should use delegate for methods inherited from X509ExtendedKeyManager when possible
by Stefan Guilhen (JIRA)
Stefan Guilhen created SECURITY-971:
---------------------------------------
Summary: SecurityKeyManager should use delegate for methods inherited from X509ExtendedKeyManager when possible
Key: SECURITY-971
URL: https://issues.jboss.org/browse/SECURITY-971
Project: PicketBox
Issue Type: Bug
Components: JBossSX
Affects Versions: PicketBox_5_0_1.Final
Reporter: Stefan Guilhen
Assignee: Stefan Guilhen
Fix For: PicketBox_5_0_2.Beta1
SecurityKeyManager now extends X509ExtendedKeyManager but the methods inherited from this class have been left unimplemented (i.e. return null).
The implementation should check if the delegate instance is of type X509ExtendedKeyManager and use the delegate for these methods instead of relying on the default implementation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1566) Unable to lookup Stateless KieSession and KieBase from Remote Java Client
by Dhamodharan Krishnan (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1566?page=com.atlassian.jira.plugi... ]
Dhamodharan Krishnan commented on DROOLS-1566:
----------------------------------------------
[~tirelli]
Could you please let me know if there is an option to lookup Stateless Kie Session.
> Unable to lookup Stateless KieSession and KieBase from Remote Java Client
> -------------------------------------------------------------------------
>
> Key: DROOLS-1566
> URL: https://issues.jboss.org/browse/DROOLS-1566
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.5.0.Final
> Reporter: Dhamodharan Krishnan
> Assignee: Edson Tirelli
>
> The rules that I define in Stateful or the default KieSession and KieBase are picked up the Remote Java client. The rules that I define in Stateless KieSessions or KieBase are not picked up.
> I am not able to define rules in Stateless Kie Session. And I get duplicate data as part of my response as the facts injected into the Working memory seems to get bundled.
> For eg, if a response POJO is supposed to contain 3 inner objects as part of its Response.
> Response.java
> {
> List<Person> personsList;
> }
> Lets assume that the response should contain 3 matching persons as part of its response.
> But each time, I hit the Kie Container from the Remote Java client, the results get bundled and it goes in Arithmetic progression as
> 3 , 6, 9, 12, 15, .... and so on until I restart my KieServer instance itself.
> Thats where I am not clear on how to configure the KieContainer to make sure the results are not bundled.
> Imagine, if I am going to call the Kie Container from different instances, it may even be giving wrong results .
> As it returns the stocked up data.
> Hope you understand my problem.
> Thats where I try to configure Stateless KieSession and map my package to that.
> But the remote Java client is not able to pick the Stateless KieSession.
> It picks only Stateful ones.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8778) Elytron filesystem-realm should load existing identities from file system
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-8778?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-8778:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
> Elytron filesystem-realm should load existing identities from file system
> -------------------------------------------------------------------------
>
> Key: WFLY-8778
> URL: https://issues.jboss.org/browse/WFLY-8778
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
> Labels: filesystem-realm, security-realm
> Fix For: 11.0.0.Beta1
>
>
> Elytron {{filesystem-realm}} should load existing identities from file system. The steps to reproduce results in:
> {noformat}
> [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:read-identity
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"elytron\"),
> (\"filesystem-realm\" => \"realm\"),
> (\"identity\" => \"user\")
> ]' not found",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:add
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY01000: Identity with name [user] already exists.",
> "rolled-back" => true
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8798) CLI Opertation 'load' for Elytron key-store does not change key used by management
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-8798?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-8798:
-----------------------------------
Fix Version/s: 11.0.0.Beta1
> CLI Opertation 'load' for Elytron key-store does not change key used by management
> ----------------------------------------------------------------------------------
>
> Key: WFLY-8798
> URL: https://issues.jboss.org/browse/WFLY-8798
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
> Labels: management-model, ssl
> Fix For: 11.0.0.Beta1
>
>
> When keystore (or cerficate in keystore) is changed during server runtime then CLI opertation {{load}} can be used for {{/subsystem=elytron/key-store=...}} to re-reading this keystore in server. However after calling this operation server still works with original keystore/certificate. Then CLI reads current keystore correctly, but in case when ssl-context which uses that key-store is used then original keystore is still used by server. Reload of server is required to correctly re-read the new keystore. See Steps to Reproduce for more details.
> We request blocker flag since this issue blocks RFE EAP7-455.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month