[
https://issues.apache.org/jira/browse/TS-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850133#comment-13850133
]
James Peach commented on TS-2437:
---------------------------------
I was suggesting that plumbing an API to obtain the certificate would let you
do this as part of your larger certificate mechanism, but I don't think that
actually makes sense :)
One concern that I have is that this seems tailored to a specific need that you
have in your environment. I wonder how this fits into a coherent SSL
configuration API? I wonder whether this could be framed in terms of the Linux
keyutils API, and use that to attach the KMS policy?
> Expose API to set keys for session ticket
> -----------------------------------------
>
> Key: TS-2437
> URL: https://issues.apache.org/jira/browse/TS-2437
> Project: Traffic Server
> Issue Type: Task
> Components: SSL
> Reporter: Wei Sun
>
> Expose API for plugin to set/refresh the keys, for security needs.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
