[JBoss JIRA] (WFLY-7194) Simplify creation of trust/key-manager in elytron
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7194?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFLY-7194:
------------------------------------
Can you, please, elaborate on "jvm-unportable" argument? I still don't get that. What I am suggesting here is to use implicitly {{TrustManagerFactory.getDefaultAlgorithm()}} in elytron code in case when user does not fill {{algorithm}} attribute explicitly in configuration. {{TrustManagerFactory.getDefaultAlgorithm()}} is IMO portable; on oracle java returns "SunX509" on ibm java "IbmX509".
Why do you expect {{algorithm}} to change to required, once such default handling would be introduce?
> Simplify creation of trust/key-manager in elytron
> -------------------------------------------------
>
> Key: WFLY-7194
> URL: https://issues.jboss.org/browse/WFLY-7194
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Fix For: 11.0.0.Alpha1
>
>
> If I want to setup TLS [1], I have to create key manager with CLI command
> {code}
> /subsystem=elytron/key-managers=httpsKM:add(key-store=httpsKS,algorithm="SunX509")
> {code}
> 1. It seems to me {{algorithm}} can be optional. If not set {{TrustManagerFactory.getDefaultAlgorithm()}} can be used.
> 2. Also, please, enhance xsd/model documentation with clear statement that this {{password}} attribute is in fact "key password" . Or probably better rename attribute from {{password}} to {{key-password}} to make it absolutely clear to everyone.
> 3. {{key-store}} attribute is declared optional in xsd . In model it is properly declared as required. Please change XSD to express it is required.
> {code}
> <xs:attribute name="key-store" type="xs:string" use="optional">
> <xs:annotation>
> <xs:documentation>
> Reference to the KeyStore to use with the KeyManager.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> {code}
> 4.{{password}} attribute is optional, probably should be required
> {code}
> "password" => {
> "type" => STRING,
> "description" => "The password to use when initialising the underlying KeyManagerFactory.",
> "expressions-allowed" => true,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "1.0.0",
> "reason" => "Will be updated to use proper CredentialStore references."
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {code}
> [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
- 1
- 0
[JBoss JIRA] (WFLY-67) method-params containing an array not correctly processed for EJB2.1 with CMT
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-67?page=com.atlassian.jira.plugin.sy... ]
RH Bugzilla Integration commented on WFLY-67:
---------------------------------------------
Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1180565|https://bugzilla.redhat.com/show_bug.cgi?id=1180565] from POST to MODIFIED
> method-params containing an array not correctly processed for EJB2.1 with CMT
> -----------------------------------------------------------------------------
>
> Key: WFLY-67
> URL: https://issues.jboss.org/browse/WFLY-67
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Environment: JBoss 7.2.0-Final Prerelease (Commit 4ed76c) and JBoss 7.1.3.Final on Win7/64 JDK 1.7.0_09
> Reporter: Robert Panzer
> Assignee: Ondrej Zizka
> Fix For: 8.0.0.Alpha1
>
> Attachments: cmt-never-array-params.zip
>
>
> It seems that the method-params for container transactions are not matched correctly if the contain arrays.
> I've got an EJB "First" that calls another EJB "Second". Both have the same interface containing a method void test(String[]);
> If I define the transaction attribute NEVER including method-params for "First" and without params for "Second" the test fails with
> JBAS014163: Transaction present on server in Never call (EJB3 13.6.2.6)
> I define the container transaction like this:
> <container-transaction>
> <method>
> <ejb-name>FirstWithParams</ejb-name>
> <method-intf>Local</method-intf>
> <method-name>test</method-name>
> <method-params>
> <method-param>java.lang.String[]</method-param>
> </method-params>
> </method>
> <method>
> <ejb-name>FirstWithParams</ejb-name>
> <method-intf>Local</method-intf>
> <method-name>test</method-name>
> <method-params>
> <method-param>java.lang.String</method-param>
> </method-params>
> </method>
> <method>
> <ejb-name>FirstWithParams</ejb-name>
> <method-intf>Local</method-intf>
> <method-name>test</method-name>
> <method-params>
> <method-param>int</method-param>
> </method-params>
> </method>
> <method>
> <ejb-name>Second</ejb-name>
> <method-intf>Local</method-intf>
> <method-name>test</method-name>
> </method>
> <trans-attribute>Never</trans-attribute>
> </container-transaction>
> I will attach a test case that fails at the call to test(String[]) but successfully call test(String) and test(int).
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
- 1
- 0
[JBoss JIRA] (REMJMX-121) Ensure anonymous authentication will only be used if a callback handler has not been specified and no credentials have been provided
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/REMJMX-121?page=com.atlassian.jira.plugin... ]
Farah Juma updated REMJMX-121:
------------------------------
Git Pull Request: https://github.com/jbossas/remoting-jmx/pull/24
> Ensure anonymous authentication will only be used if a callback handler has not been specified and no credentials have been provided
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: REMJMX-121
> URL: https://issues.jboss.org/browse/REMJMX-121
> Project: Remoting JMX
> Issue Type: Bug
> Components: Security
> Reporter: Farah Juma
> Assignee: Farah Juma
>
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
- 1
- 0