[teiid-issues] [JBoss JIRA] (TEIIDSB-34) Support Keycloak based OAuth authentication for OData

[ https://issues.jboss.org/browse/TEIIDSB-34?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-34. --------------------------------- Resolution: Done There were more than few things that were wrong in the previous commit. * The security-context was being created, but wrongfully assumed it was being associated with the current thread during the 'createSession' call. * Subject with Role names was being built wrong order than Teiid expects. Fixed that. * Since we are using "spring-security", give the security help a new security-domain name and use that elsewhere such that that will be used. Note that, in the container world, since we are using single VDB per container VDB level security domain is not workable. Maybe we should ignore this during the migration of the .vdb to .DDL if one is set. * Also using correct baseName if security-context is available during the Teiid's createSession call. * The authentication order in Web Interceptors was wrong. The auth filter needs to come before the odata filter. -- This message was sent by Atlassian Jira (v7.12.1#712002)