[ https://issues.jboss.org/browse/TEIID-5131?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5131: --------------------------------------- We have a couple of options for routes / security: 1. stick with the current approach of creating a user account for all service access, and expose a route by default for odata access. 2. provide a route that is secured with the oauth proxy side car - https://github.com/openshift/oauth-proxy - which I need to understand a little more how to pass the basic auth credentials as likely still want to have the generated user account. 3. provide os sso integration - however most other examples demonstrate creating an sso instance (sso+eap) rather than reusing internal os sso Since we aren't yet dealing with data roles all are valid. However once data roles come into the picture we need also authenticate the incoming user into Teiid, not just to a proxy. -- This message was sent by Atlassian JIRA (v7.5.0#75005)