[
https://issues.apache.org/jira/browse/JUDDI-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree resolved JUDDI-608.
------------------------------
Resolution: Unresolved
Assignee: Alex O'Ree (was: Kurt T Stam)
Unless someone wants this features, let's just add this to the back burner
> 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: Alex O'Ree
> Fix For: 3.3
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
