Great that this is at least considered. This is really an issue. I currently have a problem with a client, where we need to transfer files via sftp into Jedox. We could use a simple cloud account from a 3rd party provider, but they do not want an additional service provider. Haning out the one and only key just to push files from a subsystem is not a great idea. We should really have this.
Jedox customers work with multiple data providers. For security reasons, it is not possible to the same key with multiple partners. One partner could access to data of another partner.
Great that this is at least considered. This is really an issue. I currently have a problem with a client, where we need to transfer files via sftp into Jedox. We could use a simple cloud account from a 3rd party provider, but they do not want an additional service provider. Haning out the one and only key just to push files from a subsystem is not a great idea. We should really have this.
I totally agree. It must be a common issue that needs to be solved. We don't want to risk giving the main password to other than admin users.
This should be mandatory. We cannot share the same sftp account with other user. it's not secure at all.
It could be great to have a master account to managed the other user account which access to different folder.
It's a very important update. Have you forecast a date ?
I can only agree with the previous speakers.
This feature clearly has to exist for data transport, etc.
It should definitly be possible to transfer data via SFTP into the Jedox cloud
without having full access to directories like olap/data, storage, etc.
=> especially for automated/scheduled data delivery
For security reasons the user for such automated transfer processes should have limitted access!
Jedox customers work with multiple data providers. For security reasons, it is not possible to the same key with multiple partners. One partner could access to data of another partner.