[teiid-issues] [JBoss JIRA] (TEIIDSB-101) OData issues with multiple visible schema

Ramesh Reddy (Jira) issues at jboss.org
Thu May 30 17:16:00 EDT 2019


    [ https://issues.jboss.org/browse/TEIIDSB-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740715#comment-13740715 ] 

Ramesh Reddy commented on TEIIDSB-101:
--------------------------------------

schema/$metadata model will not be used syndesis. But is there way pattern match to $metadata as endpoint would be good.

> OData issues with multiple visible schema
> -----------------------------------------
>
>                 Key: TEIIDSB-101
>                 URL: https://issues.jboss.org/browse/TEIIDSB-101
>             Project: Teiid Spring Boot
>          Issue Type: Quality Risk
>          Components: OData
>            Reporter: Steven Hawkins
>            Priority: Major
>             Fix For: 1.2.0
>
>
> The odata logic accommodates a subcontext specifying the schema to access.  Other logic however doesn't allow for this:
> * if multiple visible schema are exposed and have a cross reference, then the metadata links will be invalid as they are created based upon the Teiid Wildfly conventions.
> * The keycloak logic exposes /$metadata as unsecured, but any of the schema/$metadata links would require authentication.
>  



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the teiid-issues mailing list