[JBoss JIRA] Updated: (TEIID-192) Add the ability to switch the identity on connections
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-192?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIID-192:
---------------------------------
Affects Version/s: 7.0
(was: 8.x)
Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] (was: [Release Notes, Documentation (Ref Guide, User Guide, etc.)])
correcting to affect the 7.0 release. Also this, or a related issue, should cover the ability for embedded connections to pass-through the subject/security context rather than asserting teiid's.
> Add the ability to switch the identity on connections
> -----------------------------------------------------
>
> Key: TEIID-192
> URL: https://jira.jboss.org/jira/browse/TEIID-192
> Project: Teiid
> Issue Type: Feature Request
> Components: Common, JDBC Driver
> Affects Versions: 7.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 7.1
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> Based upon oracle and sql server abilities, we should offer methods to assert and newly authenticate an identity on an existing connection.
--
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
15 years, 9 months
[JBoss JIRA] Resolved: (TEIID-218) Security URL properties handling
by Steven Hawkins (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-218?page=com.atlassian.jira.plug... ]
Steven Hawkins resolved TEIID-218.
----------------------------------
Resolution: Done
post jca merge, only the credentials remain as meaningful property.
> Security URL properties handling
> --------------------------------
>
> Key: TEIID-218
> URL: https://jira.jboss.org/jira/browse/TEIID-218
> Project: Teiid
> Issue Type: Sub-task
> Components: JDBC Driver, Server
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 7.0
>
>
> Defect Tracker #24196: Security URL properties are currently a mess in that there are three properties, clientToken, credentials, and trustedPayload that are all eventually treated at the trustedPayload. This is not desirable. Instead we should pass all of the connection properties to the membership service (as a map) for access by membership domains. This would remove the need to specifically pass the trustedPayload and application name as parameters. This could also be done for connectors provided that the message or the transport containing the connection properties is encrypted.
--
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
15 years, 9 months