[
https://issues.jboss.org/browse/TEIID-4161?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4161:
---------------------------------------
Need to be resilient to processing Swagger files with security
definitions for sure.
For now it's just ignored by the import. I'm having a hard time seeing exactly
what we would need to do here unless the translator subsumed all of the possible security
logic and then was able to be selective as to when it was applied based upon the security
metadata. However that seems unnecessary as most services will be secured only by a
single security type correct? And any steps for obtaining authorization would have
already been taken.
[~dalex005] What were your expectations for this issue?
Swagger: Support security in Swagger Translator
------------------------------------------------
Key: TEIID-4161
URL:
https://issues.jboss.org/browse/TEIID-4161
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 9.0
Reporter: Ramesh Reddy
Fix For: 10.2, Open To Community
The initial version added does not support security schema of the swagger definition,
this needs to be added to the translator
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)