[
https://issues.jboss.org/browse/TEIID-3102?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-3102.
---------------------------------
Labels: Beta1 (was: )
Fix Version/s: 8.7.1
8.9
Resolution: Done
Added code to allow a single vdb through "odata" WAR file. In order to control
single VDB per WAR file do the following
1) Make a copy of
"modules/org/jboss/teiid/main/deployments/teiid-odata-{version}.WAR
2) Add new WAR file name entry in the "deployments.properties" file in same
location.
3) Edit the copied WAR file's web.xml and add "allow-vdb" property. Supply
the VDB name to allow through this WAR file
4) Edit the copied WAR file's "jboss-web.xml" file, and change the context
from "odata" to any other context of your choice.
5) You can also change the security-domain if you would like
6) Remove the original WAR file if you do not choose to have "odata" based
context available any more.
7) Start the server
Now if you issue queries like
http://host:port/<your context>/$metadata
Provide a facility to restrict OData access to defined VDB
-----------------------------------------------------------
Key: TEIID-3102
URL:
https://issues.jboss.org/browse/TEIID-3102
Project: Teiid
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: OData
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Labels: Beta1
Fix For: 8.7.1, 8.9
The current OData interface in the Teiid provides one context for the web-application,
thus restricting additional security/per VDB.
The alternative proposed is restrict the current web-app to single VDB, then provide a
mechanism to alter the context and any necessary security domain stuff.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)