[teiid-issues] [JBoss JIRA] Created: (TEIID-388) When determining kestore algorithm, the logic wasn't considering the setting "ssl.KeyManagerFactory.algorithm" for defining an algorithm to use

[Van Halbert (JIRA)]

When determining kestore algorithm, the logic wasn't considering the setting "ssl.KeyManagerFactory.algorithm" for defining an algorithm to use 
------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: TEIID-388
                 URL: https://jira.jboss.org/jira/browse/TEIID-388
             Project: Teiid
          Issue Type: Bug
          Components: Common
    Affects Versions: 6.1.0
            Reporter: Van Halbert
            Assignee: Van Halbert


This is a rolled forward change from 5.5.4.   

The problem was discovered when running on an IBM Z900 machine using the IBM jdk.   It uses the Security property  "ssl.KeyManagerFactory.algorithm" to specify the algorithm to use, and our logic doesn't include an alternative when the metamatrix algorithm property is not defined, it always defaulted to "SunX509".

Therefore, the change is to check the Security property as an override to the default, but the metamatrix property will be the override to all.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira