January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3913) Support OAuth security on OData interface using Keycloak

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3913?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3913: ------------------------------------- Yes, we would need to pull in, when I started this was pulling in much more in terms of dependencies, thus I refrained adding the fix version as it would need a slightly different dependencies, but in the end it came with out any dependencies. In general I need to talk to you about the approach I took. I wrote the documentation in 8.12.Final here [https://docs.jboss.org/author/display/teiid812final/OAuth2+based+security...] but after the completion of all edits to document this needs to be pulled into the master and 8.13 > Support OAuth security on OData interface using Keycloak > -------------------------------------------------------- > > Key: TEIID-3913 > URL: https://issues.jboss.org/browse/TEIID-3913 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.13, 8.12.5 > > > Provide OAuth based security on Teiid's OData interface using Keycloak technology. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3913) Support OAuth security on OData interface using Keycloak

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3913?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3913: --------------------------------------- Do you want this in 8.13/master as well? > Support OAuth security on OData interface using Keycloak > -------------------------------------------------------- > > Key: TEIID-3913 > URL: https://issues.jboss.org/browse/TEIID-3913 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.12.5 > > > Provide OAuth based security on Teiid's OData interface using Keycloak technology. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3912. ----------------------------------- Fix Version/s: 8.13 Resolution: Done Pulled the changes into 8.13 as well. > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3624) No way to associate enterprise data types in dynamic vdb constructs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3624?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3624: --------------------------------------- Depending upon the needs of Designer and the progress of a more general type system overhaul, we may need to look at adding handling specifically for enterprise types. > No way to associate enterprise data types in dynamic vdb constructs > ------------------------------------------------------------------- > > Key: TEIID-3624 > URL: https://issues.jboss.org/browse/TEIID-3624 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.0 > > > I don't find any doc's on how to define enterprise data types in a dynamic vdb. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3624) No way to associate enterprise data types in dynamic vdb constructs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3624?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3624: ---------------------------------- Fix Version/s: 9.0 > No way to associate enterprise data types in dynamic vdb constructs > ------------------------------------------------------------------- > > Key: TEIID-3624 > URL: https://issues.jboss.org/browse/TEIID-3624 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.0 > > > I don't find any doc's on how to define enterprise data types in a dynamic vdb. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3912: ------------------------------------- Sure, we can pull in the change. I did not realize that you created the branch for 8.13 > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3914: ------------------------------------- What I meant was to somehow have Olingo clone version in our build, or way to override the behavior in our code base, such that we can mitigate the issue until we upgrade Olingo versions in between. > Datetime values not properly encoded in OData4 entity identifiers > ----------------------------------------------------------------- > > Key: TEIID-3914 > URL: https://issues.jboss.org/browse/TEIID-3914 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.4 > Reporter: Simon Evenepoel > Assignee: Steven Hawkins > Labels: odata, > > When the primary key of an OData entry consists of a timestamp or datetime value an odata get request returns the following error message: > java.net.URISyntaxException: Illegal character in scheme name at index n: tablename(partofkey='keyvalue',datepartofkey=2016-01-13 11:25:03.884) > For more information visit this thread on the user forums in which [~shawkins] said: > _"Actually there is an issue with our handling of building the entity id to go into the response. We are not properly encoding datatime values.''_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3912: --------------------------------------- It looks like we need the aalto-xml change and com.fasterxml.jackson.dataformat.xml module.xml change in 8.13. Do you want to pull this whole commit or just leave the old structure in place? > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3914: --------------------------------------- We'll be able to fix the read scenario locally, but without a change to olingo create would still be a problem. > Datetime values not properly encoded in OData4 entity identifiers > ----------------------------------------------------------------- > > Key: TEIID-3914 > URL: https://issues.jboss.org/browse/TEIID-3914 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.4 > Reporter: Simon Evenepoel > Assignee: Steven Hawkins > Labels: odata, > > When the primary key of an OData entry consists of a timestamp or datetime value an odata get request returns the following error message: > java.net.URISyntaxException: Illegal character in scheme name at index n: tablename(partofkey='keyvalue',datepartofkey=2016-01-13 11:25:03.884) > For more information visit this thread on the user forums in which [~shawkins] said: > _"Actually there is an issue with our handling of building the entity id to go into the response. We are not properly encoding datatime values.''_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3914: ------------------------------------- I wrote that layer in the Olingo too, but I missed that one. I can correct it upstream, but I am thinking we may need another method to quickly update the Olingo bugs locally. > Datetime values not properly encoded in OData4 entity identifiers > ----------------------------------------------------------------- > > Key: TEIID-3914 > URL: https://issues.jboss.org/browse/TEIID-3914 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.4 > Reporter: Simon Evenepoel > Assignee: Steven Hawkins > Labels: odata, > > When the primary key of an OData entry consists of a timestamp or datetime value an odata get request returns the following error message: > java.net.URISyntaxException: Illegal character in scheme name at index n: tablename(partofkey='keyvalue',datepartofkey=2016-01-13 11:25:03.884) > For more information visit this thread on the user forums in which [~shawkins] said: > _"Actually there is an issue with our handling of building the entity id to go into the response. We are not properly encoding datatime values.''_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016