[
https://issues.apache.org/jira/browse/JUDDI-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664283#comment-13664283
]
Kurt T Stam commented on JUDDI-608:
-----------------------------------
This would break UDDI v3 compliancy? I guess it would be a "vendor specific
feature"?
> add support for tModels with encrypted values
> ---------------------------------------------
>
> Key: JUDDI-608
> URL: https://issues.apache.org/jira/browse/JUDDI-608
> Project: jUDDI
> Issue Type: New Feature
> Reporter: Alex O'Ree
> Assignee: Kurt T Stam
>
> the idea is that we would have some kind of need to store binding template
> specific information that is encrypted. The easiest place to store this would
> be in a tmodel instance. Maybe we can have a special key that juddi
> recognizes and will automatically encrypt it. Then extensions or plugins
> would then call some api to decrypt the setting.
> i see this being particularly useful for subscription callback extensions,
> such as to a message broker that requires authentication
--
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
