You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 25, 2021. It is now read-only.
I find that we need a resource type to upload files, this files can be used for:
Generic use cases: external monitors, certificate revocation lists, certificates, private keys, external data groups ...
ASM specific cases: Import a security policy, Import a signature set
Checking our current packages I find that we already have the functionality in the f5-sdk. I understand it should be a matter of exposing f5/bigip/shared/file_transfer.py in a HEAT resource-type.
I find we should add a generic file transfer functionality in our HEAT templates roadmap. If we think in SSL alone I would say that half of our devices are likely to have a SSL config in them / hence their own private keys & certs.
Hi
I find that we need a resource type to upload files, this files can be used for:
Generic use cases: external monitors, certificate revocation lists, certificates, private keys, external data groups ...
ASM specific cases: Import a security policy, Import a signature set
Checking our current packages I find that we already have the functionality in the f5-sdk. I understand it should be a matter of exposing f5/bigip/shared/file_transfer.py in a HEAT resource-type.
I find we should add a generic file transfer functionality in our HEAT templates roadmap. If we think in SSL alone I would say that half of our devices are likely to have a SSL config in them / hence their own private keys & certs.
Thanks