[JBoss JIRA] Updated: (TEIID-966) User (principal) name in MetaMatrix should be consistently the same string
by Ramesh Reddy (JIRA)
[ https://jira.jboss.org/browse/TEIID-966?page=com.atlassian.jira.plugin.sy... ]
Ramesh Reddy updated TEIID-966:
-------------------------------
Fix Version/s: 7.1
Affects Version/s: 7.0
> User (principal) name in MetaMatrix should be consistently the same string
> --------------------------------------------------------------------------
>
> Key: TEIID-966
> URL: https://jira.jboss.org/browse/TEIID-966
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.0
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 7.1
>
>
> The issue has to do with the way we represent a user's name. Customer uses LDAP for a membership domain. Sometimes, the user's name is their cn, followed by "@" plus the domain name, e.g.:
> username@LDAP
> Sometimes, it's simply the user name. e.g.:
> username
> This name is recorded in the audit logs, used throughout Console, and perhaps most importantly, is the name returned by the USER() system function.
> The problem is that we use the return value of USER() to record information about who is doing things. Later, we make comparisons against this info to control access, etc. This comparison often fails, even though we may be comparing the same identity, due to this inconsistency.
> Workaround for the USER() function: build in special logic within each procedure to strip out the @LDAP if it is present.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Updated: (TEIID-999) Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors
by Ramesh Reddy (JIRA)
[ https://jira.jboss.org/browse/TEIID-999?page=com.atlassian.jira.plugin.sy... ]
Ramesh Reddy updated TEIID-999:
-------------------------------
Fix Version/s: 7.1
> Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors
> ---------------------------------------------------------------------------------
>
> Key: TEIID-999
> URL: https://jira.jboss.org/browse/TEIID-999
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Environment: MS Excel 2003
> Reporter: Larry O'Leary
> Fix For: 7.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Create a capabilities set that can be used by the MS Access and MS Excel connectors. We currently offer the MS Excel connector which is using the generic JDBC capabilities and translators and the MS Access connector which is using its own capabilities and translators but they do not reflect MS Access.
> The replacement connector types should work very much like the current ones but reflect the base capabilities offered by MS JET 4 and specific capabilities as defined by the MS Excel and MS Access limitations to the MS JET 4 implementation. At bare minimum we should support push-down of all currently defined capabilities and remove any current ones that are not valid for MS JET/MS Access/MS Excel.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months