Major Description
Currently, when using the management protocol to create new SSL-profiles, those profiles must access certificate files that are already placed in the file system. In other words, in order to create an SSL-profile on a running router, files must first be placed on the file system in a location accessible by the router. This may be problematic in cases where the router is remote from the managing agent, or when containerization limits access to the router's underlying file system.
This new feature allows a managing agent to remotely inject files into a running router to be stored in temporary file storage. These files are usable in sslProfile management entities (by specifying the files without an absolute path). The temporary files are removed from the file system on router shutdown.