Describe the bug
Import configurations (and mapping files) are currently not associated to specific clients but instead available system wide to all users of all clients. This is in contrast to how templates, workflows, rulesets and dockets are managed in Kitodo.Production, which are all assigned to specific clients. The same should be the case for import configurations and mapping files. It is especially import for import configurations because they can contain sensitive information like passwords for access restricted ftp servers.
To Reproduce
Steps to reproduce the behavior:
Create an import configuration
Change the current client
See import configuration created with different client is still available for other client as well
Expected behavior
Import configurations and mapping files should be associated to specific clients, the same as templates, workflows and rulesets.
Describe the bug Import configurations (and mapping files) are currently not associated to specific clients but instead available system wide to all users of all clients. This is in contrast to how templates, workflows, rulesets and dockets are managed in Kitodo.Production, which are all assigned to specific clients. The same should be the case for import configurations and mapping files. It is especially import for import configurations because they can contain sensitive information like passwords for access restricted ftp servers.
To Reproduce Steps to reproduce the behavior:
Expected behavior Import configurations and mapping files should be associated to specific clients, the same as templates, workflows and rulesets.
Release All releases