[JBoss JIRA] Updated: (TEIID-323) PSC nomenclature is underused and confusing and complex
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-323?page=com.atlassian.jira.plug... ]
Van Halbert updated TEIID-323:
------------------------------
Fix Version/s: 6.1.0
(was: 6.2.0)
Affects Version/s: 6.1.0
(was: 6.0.0)
> PSC nomenclature is underused and confusing and complex
> -------------------------------------------------------
>
> Key: TEIID-323
> URL: https://jira.jboss.org/jira/browse/TEIID-323
> Project: Teiid
> Issue Type: Task
> Components: Console, Server
> Affects Versions: 6.1.0
> Reporter: Ramesh Reddy
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 6.1.0
>
>
> Currently there is possibility in the configuration to bundle multiple services under some thing called PSC which is a grouping of the services. This feature is introduces lot of unnecessary complexity in the code, and using the Console with these confusing.
> .
> If you ever navigated between "MetaMatrixFullServer" and "QueryServer" and "ODBCServer" and/or configuring the connectors for those you know the pain.
> The original intent was to move a bundle of connectors from one server to another. Now a days connectors are always bundled with their VDBs. We can reduce this complexity in code and UI.
> Suggestions are welcome how we can reduce this clutter.
--
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] Updated: (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 updated TEIID-218:
---------------------------------
Fix Version/s: 6.2.0
(was: 6.1.0)
> Security URL properties handling
> --------------------------------
>
> Key: TEIID-218
> URL: https://jira.jboss.org/jira/browse/TEIID-218
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Driver, Server
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.2.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