[JBoss JIRA] (TEIID-2803) Provide SAML support for OData Transport
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2803?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2803:
-------------------------------------
My goal for this JIRA was to use Picketlink as Service Provider and use any other external IDP like Shibboleth, OpenAM (OpenSSO) to do a real world scenario. Here is what I have been tried so far.
Picket Link:
* All the examples show Picketlink IDP and Picketlink SP. I have asked for example with other IDP here https://community.jboss.org/thread/236380 so far nobody replied. It seems to me that Picketlink team only verified with their own IDP and SP. It may work with others but no such examples found. I found couple threads (https://community.jboss.org/thread/163295?tstart=0) where community users were trying to work with Shibboleth but not much further info than look at the code. If I was the security expert I could have -:(
* I tried with my very limited SAML knowledge TestShib (http://www.testshib.org) a Shibboleth as IDP and PicketLink as SP with sales-metadata example that PicketLink provides with modifications to sp-metadata and certificates etc, but this was with no success. I suspect my configuration was wrong, but can not verify it authoritatively.
* Picketlink seems to provide different types of examples, plain, using certificates and using metadata. Shibboleth had one way, which was similar to metadata example. So, it was little confusing as to why separate examples. IMO, interoperabilty should be one of the main features of these products, as more users will be developing the SP to work with their enterprise IDP.
* I gave up and finally tried Picketlink IDP with Picketlink SP, the examples worked fine within few minutes, except for one example that "metadata" based. It seemed like IDP and SP were redirecting to each other in a loop after the authentication. For me this was only example I really cared (see above for my reason)
* My another requirement was to support OAuth2, not sure Picketlink provides that.
* Picketlink also provides "subsystem" for JBoss EAP 6.1. I installed and tried an example. I did like the way how this was supported. In this scenario, the SP developer does NOT need to configure anything in their WAR files, all the configuration is done in standalone.xml file which was perfect, because I did not have to do anything as SP developer. But, I found that this configuration also favors Picketlink IDP, not sure it can be used with external IDP (I have to try this next)
CXF:
* CXF seems to provide support for both SAML SSO and OAuth1 & 2
* CXF claims to their SP tested with other external vendors. I asked for a example in their community (http://cxf.547215.n5.nabble.com/Any-CXF-examples-that-show-SAML-usage-wit...) within minutes I had a response with an example.
* When I tried their example as is, I had lot of CNF exceptions in JBoss EAP 6.1, obviously I need to do lot more work here to resolve dependencies. Seems like there were lot of these.
* The bad part here is in JBoss EAP, CXF is the chosen JAX-RS implementation, so I am not sure, if I will be able to use just their security aspect of the libraries along with Resteasy and implement the feature. Otherwise downstream productization and support will be hard.
> Provide SAML support for OData Transport
> ----------------------------------------
>
> Key: TEIID-2803
> URL: https://issues.jboss.org/browse/TEIID-2803
> Project: Teiid
> Issue Type: Feature Request
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.7
>
>
> Provide SAML based security authentication support for OData transport. Provide a capability for user to configure their own STS provider.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (TEIID-2815) Need to add the aggregate functions to list of supported functions, for Designer to expose for the user
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2815?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2815:
---------------------------------------
> Would be nice to have that option handled as maybe a separate/new call... SystemFunctionManager.getAggregateFunctions() ?
It would likely need to remain separate for the time being due to the legacy separation between functions and aggregate logic, but I'm fine if you want us to add something like that. You may have to consult FunctionDescriptor.getMethod.getAggregateAttributes to know when distinct and ordering is allowed (we don't yet capture a notion of the * select all syntax as it's only supported for count\(*))
Do you use the FunctionForm class at all? If not I'll clean that up as part of this change.
> Need to add the aggregate functions to list of supported functions, for Designer to expose for the user
> -------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2815
> URL: https://issues.jboss.org/browse/TEIID-2815
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Need to add to the list, of known supported functions, what are all the aggregate functions that are supported. This list is what Teiid Designer would expose to the user for modeling purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (TEIID-2815) Need to add the aggregate functions to list of supported functions, for Designer to expose for the user
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-2815?page=com.atlassian.jira.plugin... ]
Barry LaFond commented on TEIID-2815:
-------------------------------------
We're currently using your FunctionLibrary containing SystemFunctionManager.getSystemFunctions()... then adding a user's local workspace functions.
We can programmatically use your AggregateSymbol.Type enum..... but we'd have to construct the FunctionDescriptors ourselves.
Would be nice to have that option handled as maybe a separate/new call... SystemFunctionManager.getAggregateFunctions() ?
> Need to add the aggregate functions to list of supported functions, for Designer to expose for the user
> -------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2815
> URL: https://issues.jboss.org/browse/TEIID-2815
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Need to add to the list, of known supported functions, what are all the aggregate functions that are supported. This list is what Teiid Designer would expose to the user for modeling purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months
[JBoss JIRA] (TEIID-2814) HIVE: quote is removed for TIMESTAMP field in where clause
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2814?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-2814:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1058084
> HIVE: quote is removed for TIMESTAMP field in where clause
> -----------------------------------------------------------
>
> Key: TEIID-2814
> URL: https://issues.jboss.org/browse/TEIID-2814
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: HIVE and Teiid 8.6
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.7
>
>
> I am running teiid 8.6 against HIVE. And I found out that quote was removed for TIMESTAMP field in where clause. And it caused java.sql.SQLException: Error while processing statement: FAILED: ParseException line 1:88 missing EOF
> Original SQL:
> select "the_date",
> "store_sales"
> from "hive2"."sales_seq"
> where ("the_date" > '1970-05-16 00:10:04')
> Teiid generated SQL:
> SELECT g_0.the_date, g_0.store_sales FROM sales_seq g_0 WHERE g_0.the_date > 1970-05-16 00:10:04.0
> Exception:
> Caused by: java.sql.SQLException: Error while processing statement: FAILED:
> ParseException line 1:88 missing EOF at '00' near '16'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 11 months