There is problem with SMIME::CertPath, which is on host file system /etc/ssl/otrs/certs , I looked on vanilla Otobo installation and this settings is disabled.
During migration of OTRS settings is this migrated and enabled.
Diese Antwort wurde geändert vor 3 Monaten, 3 Wochen von Marc Nilius.
firstly, I assume that the SecureMode problem arises from the SMIME::CertPath setting which likely is invalid on the new server. In general if settings are invalid one has to fiddle around by hand a bit. I don’t know if there is “the” best way to handle this, in your case I would probably use
to Kernel/Config.pm, to be able to use the SysConfig in the WebInterface if you prefer that to the console.
Regarding SMIME::CertPath – I shortly discussed this with the others. In principle for settings like this, we have the choice of trying to migrate it, or reset it to the OTOBO default. For SMIME certificates it is quite clear, that you will want to use them from OTOBO, too, so I would rather not just deactivate this setting. As we cannot create arbitrary directories in the file system, however (e.g. “/etc/ssl/otrs/certs”) this in my opinion has to be prepared prior to the migration. We will include it in the migration manual.
because I lost half of one post during editing, there is one important information missing. I have Docker install, do I need to map that folder to be “visible” inside of the containers ?
just quickly to not let it unanswered: For Docker there is the possibility to mount directories into the Docker environment somehow. But I’m no expert there, it’s definitely something we have to think about, I guess. Stefan earlier suggested to store those variables in /opt/otobo/var/certs or similar, but that doesn’t help you with the migration, now, of course. (For the moment I would reset the setting as described above, and then reconfigure it.) If he finds time, Stefan will probably write a suggestion, too.