[teiid-issues] [JBoss JIRA] Commented: (TEIID-472) Teiid Embedded unable to login to JDBC data sources requiring username/password

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-472:
------------------------------------

This occurring because of Embedded while loading is not correctly reading the configuration from its configuration file. To work around, in the Teiid Embedded "deploy" directory

Workaround: (1)

1) Make a back up copy of the "configuration.xml"
2) Edit the "configuration.xml" file, and remove the fragment of the "connector" you are having issues with. For example, you are getting userid/password issues with "Oracle" data source, you can delete "Oracle Connector", then the Embedded solely depends on the configuration for this connector based on what supplied within the VDB and that should work fine. 

Workaround: (2)

You can edit the VDB file using the zip utility, and edit the "ConfigurationInfo.def" file, and in "password" lines of that file, put plain text password.

note these are only temporary workarounds. 



> Teiid Embedded unable to login to JDBC data sources requiring username/password
> -------------------------------------------------------------------------------
>
>                 Key: TEIID-472
>                 URL: https://jira.jboss.org/jira/browse/TEIID-472
>             Project: Teiid
>          Issue Type: Bug
>          Components: Embedded
>    Affects Versions: 6.0.0
>         Environment: fedora 10, Teiid Designer 040709, Teiid 6.0.0
>            Reporter: Paul Nittel
>            Assignee: Ramesh Reddy
>             Fix For: 6.1.0
>
>
> I took the PartsSupplier_VDB from the Designer and tried to use it in Teiid Embedded. Using a simple JDBC query tool, I was unable to login to the data sources (Oracle and SQL Server). Working with Ramesh, we found we could edit the configuration.def inside the VDB and edit the mm-encrypted password to plain text and it would work. As an alternative, we could use the configuration.xml file from the Designer and that worked.
> Ramesh will fill in the technical details...

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