[JBoss JIRA] (TEIID-5742) Info log on each unauthenticated action
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5742?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5742:
-------------------------------------
I see below in "teiid-komodo" image run every second or so, I believe with rediness-check
{code}
2019-05-14 15:10:45.538 INFO 1 --- [nio-8080-exec-8] i.j.internal.reporters.LoggingReporter : Span reported: 41943d118563ddce:41943d118563ddce:0:1 - GET
{code}
> Info log on each unauthenticated action
> ---------------------------------------
>
> Key: TEIID-5742
> URL: https://issues.jboss.org/browse/TEIID-5742
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Probably due to the recent changes to secure jdbc/pg in Teiid Spring Boot, I'm now seeing logs like:
> 2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
> 2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
> ...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIID-5742) Info log on each unauthenticated action
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5742?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5742:
---------------------------------------
> I also see one log message with each open tracing SPAN
What is that message?
> Maybe we can configure these to WARN level?
This one is not an issue of level. We typically have run embedded with the DoNothingSecurityHelper, which creates a dummy context/subject - so the check in LocalServerConnection passes. With the SpringSecurityHelper and a completely unauthenticated action, there is no context/subject.
> Info log on each unauthenticated action
> ---------------------------------------
>
> Key: TEIID-5742
> URL: https://issues.jboss.org/browse/TEIID-5742
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Probably due to the recent changes to secure jdbc/pg in Teiid Spring Boot, I'm now seeing logs like:
> 2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
> 2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
> ...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIID-5742) Info log on each unauthenticated action
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5742?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5742:
-------------------------------------
I also see one log message with each open tracing SPAN. Maybe we can configure these to WARN level?
> Info log on each unauthenticated action
> ---------------------------------------
>
> Key: TEIID-5742
> URL: https://issues.jboss.org/browse/TEIID-5742
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Probably due to the recent changes to secure jdbc/pg in Teiid Spring Boot, I'm now seeing logs like:
> 2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
> 2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
> ...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIID-5742) Info log on each unauthenticated action
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5742?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5742:
----------------------------------
Description:
Probably due to the recent changes to secure jdbc/pg in Teiid Spring Boot, I'm now seeing logs like:
2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
...
was:
Probably due to the recent changes to secure jdbc/pg, I'm now seeing logs like:
2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
...
> Info log on each unauthenticated action
> ---------------------------------------
>
> Key: TEIID-5742
> URL: https://issues.jboss.org/browse/TEIID-5742
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Probably due to the recent changes to secure jdbc/pg in Teiid Spring Boot, I'm now seeing logs like:
> 2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
> 2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
> ...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIID-5742) Info log on each health check
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5742?page=com.atlassian.jira.plugin... ]
Steven Hawkins moved TEIIDSB-88 to TEIID-5742:
----------------------------------------------
Project: Teiid (was: Teiid Spring Boot)
Key: TEIID-5742 (was: TEIIDSB-88)
Fix Version/s: 12.3
(was: 1.1.0)
> Info log on each health check
> -----------------------------
>
> Key: TEIID-5742
> URL: https://issues.jboss.org/browse/TEIID-5742
> Project: Teiid
> Issue Type: Quality Risk
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Probably due to the recent changes to secure jdbc/pg, I'm now seeing logs like:
> 2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
> 2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
> ...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIID-5742) Info log on each unauthenticated action
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5742?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5742:
----------------------------------
Summary: Info log on each unauthenticated action (was: Info log on each health check)
> Info log on each unauthenticated action
> ---------------------------------------
>
> Key: TEIID-5742
> URL: https://issues.jboss.org/browse/TEIID-5742
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Probably due to the recent changes to secure jdbc/pg, I'm now seeing logs like:
> 2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
> 2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
> ...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIID-5742) Info log on each health check
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5742?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5742:
----------------------------------
Component/s: Query Engine
> Info log on each health check
> -----------------------------
>
> Key: TEIID-5742
> URL: https://issues.jboss.org/browse/TEIID-5742
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Probably due to the recent changes to secure jdbc/pg, I'm now seeing logs like:
> 2019-05-14 02:13:23.003 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 33UbTZhXZKkC so that the connection can be used in a different security context.
> 2019-05-14 02:13:23.004 INFO 1 --- [nio-8080-exec-8] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 638A9GlJTEtL so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.086 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 4Kc9NS+S/YcE so that the connection can be used in a different security context.
> 2019-05-14 02:13:39.090 INFO 1 --- [nio-8080-exec-9] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session SL9YhfKOtGGw so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.997 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session Z41j3peTbpHP so that the connection can be used in a different security context.
> 2019-05-14 02:13:42.998 INFO 1 --- [io-8080-exec-10] org.teiid.SECURITY : TEIID40115 Local pass-through connection implicitly closing session 8XDWPXCiLYwz so that the connection can be used in a different security context.
> ...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIID-5734) Planning errors with masking due to unaliased column references
by Johnathon Lee (Jira)
[ https://issues.jboss.org/browse/TEIID-5734?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-5734:
---------------------------------
Fix Version/s: 8.12.18.6_4
> Planning errors with masking due to unaliased column references
> ---------------------------------------------------------------
>
> Key: TEIID-5734
> URL: https://issues.jboss.org/browse/TEIID-5734
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 12.2, 11.2.3, 8.12.18.6_4, 12.1.2
>
>
> The ColumnMaskingHelper is creating expressions using the unaliased source name. This implicitly is relying on other logic, such as the raising of an access node to compensate for that. If however a view layer with masking is used that has no access nodes or cannot be removed, then exceptions will occur if it appears in the user query aliased and with constructs above, such as an order by.
> For example with the vdb:
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <vdb name="odatacm" version="1">
> <description>Test column masking for Odata </description>
> <property name="validationDateTime" value="Thu May 02 14:13:21 CDT 2019"/>
> <property name="validationVersion" value="8.12.13"/>
> <model name="vw" type="VIRTUAL">
> <metadata type="DDL"><![CDATA[
> CREATE VIEW employee (
> id integer,
> name string,
> taxid string,
> taxid_cd string,
> CONSTRAINT pk_id PRIMARY KEY(id)
> ) OPTIONS(UPDATABLE 'TRUE')
> AS
> SELECT
> 1 AS id, 'Debbie' AS name, '123456789' AS taxid, 'SSN' AS taxid_cd
> UNION
> SELECT
> 2 AS id, 'Mide' AS name, '234567891' AS taxid, 'FED' AS taxid_cd
> UNION
> SELECT
> 3 AS id, 'DJS' AS name, '345678912' AS taxid, 'FED' AS taxid_cd
> UNION
> SELECT
> 4 AS id, 'Joe' AS name, '456789123' AS taxid, 'SSN' AS taxid_cd;
> ]]></metadata>
> </model>
> <data-role allow-create-temporary-tables="false" any-authenticated="true" grant-all="false" name="Data Role 1">
> <description/>
> <permission>
> <resource-name>vw.employee.taxid</resource-name>
> <condition>vw.employee.id>2</condition>
> <mask order="0">'Blocked'</mask>
> </permission>
> <permission>
> <resource-name>vw</resource-name>
> <allow-create>false</allow-create>
> <allow-read>true</allow-read>
> <allow-update>false</allow-update>
> <allow-delete>false</allow-delete>
> <allow-execute>false</allow-execute>
> <allow-alter>false</allow-alter>
> </permission>
> <permission>
> <resource-name>sysadmin</resource-name>
> <allow-create>false</allow-create>
> <allow-read>false</allow-read>
> <allow-update>false</allow-update>
> <allow-delete>false</allow-delete>
> <allow-execute>false</allow-execute>
> <allow-alter>false</allow-alter>
> </permission>
> </data-role>
> </vdb>
> {code}
> and the query "select * from employee as e order by id" is issued, then an exception will be returned:
> TEIID30259 Cannot introduce new expressions [vw.employee.id] in duplicate removal
> Which is a safe guard to prevent further planning errors - note the unaliased / fully qualified name in the exception message.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIIDSB-90) Add options to configure pg/jdbc secure transports
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-90:
-------------------------------------
Summary: Add options to configure pg/jdbc secure transports
Key: TEIIDSB-90
URL: https://issues.jboss.org/browse/TEIIDSB-90
Project: Teiid Spring Boot
Issue Type: Sub-task
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 1.1.0
Based upon TEIIDSB-86 the core needs to be capable of providing an ssl enabled transport (for use with an sni route, loadbalancer, etc.).
It will be a separate issue to tie this into a particular openshift based certificate scheme (self-signed, serving-cert, etc.).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (TEIIDSB-86) Plans for secure socket transports
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-86?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIIDSB-86 at 5/14/19 5:37 PM:
----------------------------------------------------------------
After making a full assessment, the recommendation is to:
If end-to-end (internal and external) is needed, offer an option for 1-way secure transports using the service generated certificate. External exposure with a loadbalancer, which works for both transports with or without ssl.
If secure external only is needed, we need to be able to start both the secure and non-secure transports.
At a later time, if secure external only is needed, we could offer an option for 1-way secure transports using a stunnel with external access provided via routes - but of course that requires that clients use a stunnel client as well. The advantages here are being able to use external routes and the same transport for secure and non-secure.
was (Author: shawkins):
After making a full assessment, the recommendation is to:
If end-to-end (internal and external) is needed, offer an option for 1-way secure transports using the service generated certificate. External exposure with a loadbalancer, which works for both transports with or without ssl.
At an even later time, if secure external only is needed, we could offer an option for 1-way secure transports using a stunnel with external access provided via routes - but of course that requires that clients use a stunnel client as well.
> Plans for secure socket transports
> ----------------------------------
>
> Key: TEIIDSB-86
> URL: https://issues.jboss.org/browse/TEIIDSB-86
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.1.0
>
>
> The Teiid Spring Boot configuration allows for only non-secured pg / JDBC socket transports. For external client scenarios and even for varying degrees of compliance with intra-cluster traffic, a secure layer may be required.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months