[teiid-issues] [JBoss JIRA] Commented: (TEIID-550) Connector passwords encrypted by Teiid Designer are not properly decrypted by Teiid standalone runtime.

[Ken Johnson (JIRA)]

    [ https://jira.jboss.org/jira/browse/TEIID-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465862#action_12465862 ] 

Ken Johnson commented on TEIID-550:
-----------------------------------

TEIIDDES-136 describes a general problem, the solution to which may solve the problem of the encrypted password in Configurationinfo.def not being decrypted.  The final line in Ramesh's last comment captures the issue.   In the VDB I've created, Configurationinfo.def does have a component definition for the MySQL connector - so that may have been corrected since 136 was originally logged.  



> Connector passwords encrypted by Teiid Designer are not properly decrypted by Teiid standalone runtime.  
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-550
>                 URL: https://jira.jboss.org/jira/browse/TEIID-550
>             Project: Teiid
>          Issue Type: Bug
>    Affects Versions: 6.0.0
>         Environment: Teiid 6.0.0, JBoss AS 4.2.3, Sun JDK 1.6.0. 
>            Reporter: Ken Johnson
>            Assignee: Steven Hawkins
>
> Using Teiid Designer snapshot from 4/30, create VDB with connectors bound to local MySQL using explicit username and password.  Execution in Designer works correctly.  Deploy VDB to Teiid configured with File Path profile on JB AS 4.2.3.  Upon Teiid startup, the MySQL connector bindings fail due to bad password.  It does correctly use the MySQL username from the connector binding but the correct password is not being submitted.  
> To workaround, I edited ConfigurationInfo.def in the VDB archive file to remove the encrypted password and replace with hardcoded clear-text password.  Then the bindings were able to start correctly.
> Do Teiid Designer and Teiid share the same keystore?  If not, what is the procedure for enabling password decryption at runtime?

-- 
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