June 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3014) Honor the visibility flags in generation of in OData EDM Schema

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3014?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3014: -------------------------------- Issue Type: Bug (was: Enhancement) > Honor the visibility flags in generation of in OData EDM Schema > --------------------------------------------------------------- > > Key: TEIID-3014 > URL: https://issues.jboss.org/browse/TEIID-3014 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.7.1, 8.8 > > > Currently when EDM Metadata s generated the visibility flags were not taken into account and generates all the metadata. It should honor the user's configuration about visibility. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3014) Honor the visibility flags in generation of in OData EDM Schema

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3014?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3014. --------------------------------- Labels: Beta3 (was: ) Resolution: Done Based on the Model.isVisible() flag, the OData schema generation now skips the models with visibility flag set to false. > Honor the visibility flags in generation of in OData EDM Schema > --------------------------------------------------------------- > > Key: TEIID-3014 > URL: https://issues.jboss.org/browse/TEIID-3014 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.7.1, 8.8 > > > Currently when EDM Metadata s generated the visibility flags were not taken into account and generates all the metadata. It should honor the user's configuration about visibility. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3015) ODATA: Duplicate NavigationProperty name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3015?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3015. --------------------------------- Labels: Beta3 (was: ) Resolution: Done If the reference is on same table, the navigation is only attached at one end, and the second one is avoided. > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-3015 > URL: https://issues.jboss.org/browse/TEIID-3015 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.7.1, 8.8 > > > Entity 1: TransferRule > Entity 2: FinancialAccount > TransferRule > - sourceAccount : FinancialAccount > - destination : FinancialAccount > - other attributes > the mapping to this for odata resolves to > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" > ToRole="financialaccount" /> > The navigation property name is duplicated with in transfer rule entity. > Hence some of the Odata client see it as ambiguous element > Is there a way to customise the Name to > Name="src_financialaccount" and > Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3013) Add realm authentication to teiid-security

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3013?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3013: ------------------------------------- {code} /subsystem=security/security-domain=teiid-security:add(cache-type=default) /subsystem=security/security-domain=teiid-security/authentication=classic:add() /subsystem=security/security-domain=teiid-security/authentication=classic/login-module=RelamDirect:add(code=RealmDirect, flag=sufficient, module-options=[("password-stacking"=>"useFirstPass")]) {code} Should work. We need to think how we can run integration tests with this configuration. > Add realm authentication to teiid-security > ------------------------------------------ > > Key: TEIID-3013 > URL: https://issues.jboss.org/browse/TEIID-3013 > Project: Teiid > Issue Type: Quality Risk > Security Level: Public(Everyone can see) > Components: Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > To allow teiid to use users added by the console by default we should add the RealmDirect login module to the teiid-security security domain. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3016) Add headers parameter to invokeHttp

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3016?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3016: --------------------------------------- Since we are expected to set the headers as a map of string->list<string> it would probably be easier for us to expect a json string for the headers, rather than attempting to parse the header directly. So rather than, {code}'ContentType=application/json;Accepts=application/text'{code} {code}'{"ContentType":["application/json"],"Accepts":["application/text"]}'{code} > Add headers parameter to invokeHttp > ----------------------------------- > > Key: TEIID-3016 > URL: https://issues.jboss.org/browse/TEIID-3016 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > > There is a need to set common headers, such as content type and accepts. Since there may be other custom values it probably makes sense to do this as a generic parameter as Ramesh suggests: > call restBDM.invokeHttp(action => 'POST', endpoint => qp, headers=>'ContentType=application/json;Accepts=application/text') -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3016) Add headers parameter to invokeHttp

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3016: ------------------------------------- Summary: Add headers parameter to invokeHttp Key: TEIID-3016 URL: https://issues.jboss.org/browse/TEIID-3016 Project: Teiid Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.8 There is a need to set common headers, such as content type and accepts. Since there may be other custom values it probably makes sense to do this as a generic parameter as Ramesh suggests: call restBDM.invokeHttp(action => 'POST', endpoint => qp, headers=>'ContentType=application/json;Accepts=application/text') -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3015) ODATA: Duplicate NavigationProperty name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3015?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3015: ------------------------------------- This only happens when the table has self reference like parent child records. > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-3015 > URL: https://issues.jboss.org/browse/TEIID-3015 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Entity 1: TransferRule > Entity 2: FinancialAccount > TransferRule > - sourceAccount : FinancialAccount > - destination : FinancialAccount > - other attributes > the mapping to this for odata resolves to > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" > ToRole="financialaccount" /> > The navigation property name is duplicated with in transfer rule entity. > Hence some of the Odata client see it as ambiguous element > Is there a way to customise the Name to > Name="src_financialaccount" and > Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3013) Add realm authentication to teiid-security

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3013?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3013: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Add realm authentication to teiid-security > ------------------------------------------ > > Key: TEIID-3013 > URL: https://issues.jboss.org/browse/TEIID-3013 > Project: Teiid > Issue Type: Quality Risk > Security Level: Public(Everyone can see) > Components: Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > To allow teiid to use users added by the console by default we should add the RealmDirect login module to the teiid-security security domain. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3013) Add realm authentication to teiid-security

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3013?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3013: --------------------------------------- This seemed straight-forward, just adding {code} <login-module code="RealmDirect" flag="sufficient"> <module-option name="password-stacking" value="useFirstPass"/> </login-module> {code} Into the standalone xml, but the cli scripting is tripping me up. In the standalone cli both the current add of the login module and my update fail with "Operation 'add' does not expect any property." {code} /subsystem=security/security-domain=teiid-security/authentication=classic:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.server.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.server.config.dir}/teiid-security-roles.properties")]}]) /subsystem=security/security-domain=teiid-security/authentication=classic:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.RealmDirectLoginModule", "flag"=>"sufficient", "module-options"=>[("usersProperties"=>"${jboss.server.config.dir}/teiid-security-users.properties")]},{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.server.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.server.config.dir}/teiid-security-roles.properties")]}]) {code} Ramesh do you want to take this one or know what is going on there? > Add realm authentication to teiid-security > ------------------------------------------ > > Key: TEIID-3013 > URL: https://issues.jboss.org/browse/TEIID-3013 > Project: Teiid > Issue Type: Quality Risk > Security Level: Public(Everyone can see) > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > To allow teiid to use users added by the console by default we should add the RealmDirect login module to the teiid-security security domain. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3015) ODATA: Duplicate NavigationProperty name

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3015?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3015: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-3015 > URL: https://issues.jboss.org/browse/TEIID-3015 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Entity 1: TransferRule > Entity 2: FinancialAccount > TransferRule > - sourceAccount : FinancialAccount > - destination : FinancialAccount > - other attributes > the mapping to this for odata resolves to > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" > ToRole="financialaccount" /> > The navigation property name is duplicated with in transfer rule entity. > Hence some of the Odata client see it as ambiguous element > Is there a way to customise the Name to > Name="src_financialaccount" and > Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2014