![]() ![]() If the key does not decrypt the catalog file, you will get an error message, otherwise the import will proceed. Select your import options and click Import. The characters of the key value are hidden to keep them secret. In the right-hand panel, browse the file system to enter the catalog file you want to import.Ĭhoose the second radio button and paste the entire key value in the designated field. ![]() Select Manage > Server Settings, then click Import in the left-hand panel. Log in as system administrator ( superuser by default). The key value is its representation in hexadecimal, for example:Ġx1c 0x40 0xb9 0xf6 0xe2 0xd3 0xf9 0xd0 0x5a 0xab 0x84 0xe6 0xd4 0xe8 0x5f 0xed The simplest way to import a catalog with a custom key is to use the Settings UI for import and enter the key value. Use the import command line to import the key into the keystore so that is available for any import operation in the future. Then use the import UI with the secure file URI in the Key File field. Store the custom key as a secure file resource in the repository, so it can be reused. This method is simple, but the key will not be stored in the server for multiple imports. Use the import UI, and enter the key’s hexadecimal bytes in the Key Value field. There are three ways to import a catalog that is encrypted with a custom key: In order to import these catalogs into the latest server, you will need to give the server a copy of the custom key. The custom keys were not included in the export catalogs. Prior to version 7.5 with custom import-export keys The server handles previous export catalogs created with legacy keys, and even older catalogs that did not use encryption. The catalog includes the exporting server’s default export key, and the server uses this key to decrypt any passwords it contains during the import operation. However, there are some cases where the import key needs to be handled manually, as shown in the following table: Origin of Export Catalog Beginning with version 7.5, the server includes a copy of the key in the export catalog so that the importing server can decrypt the catalog. In previous versions of the server, the import-export key had to be configured manually and shared between servers. Overview of JasperReports Server SecurityĪs of JasperReports Server 7.5, the management of the encryption keys used during import has been automated. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |