I have many images on a ftp, I'm trying to assign each image registo. This is simple, but once you've given I have to put login and password to see each creative. I want to see all the creativities, but puttin the loging and password in one time. is this posible???

Neil, I presume you mean IOK password, rather than HTTP authentication. HTTP (server) authentication can be resolved by using Chain action.

You can't currently specify a password in File actions in the scheduler. The scheduler is designed to work with private copies of IOK files (without security measures) to which passwords and other security options are then added by the scheduler action before saving/publishing to a public location.

Oscar, please clarify - you have several images on an FTP server, and you are setting up an image set in Omniscope to access these images, using "Web" option with ftp://... URLs? If so, you can specify the username & password using the format:

ftp://username:password@domain.com/path/to/file.jpg

so typically your image set configuration would have a base URL of something like:

ftp://username:password@domain.com/path/

Hi Steve

Thanks for your reply. I understand where you are coming from but this is slightly disapointing.
This file has the most sensitive data we hold for the company and as such even the admins on our server should have limited access.

Regards
Neil

There is also another use case....clients/recipients of IOK reports submitting their updates and corrections, plus their own internal data for incorporation into the central refreshed update. Of course they would be submitting (via email or even better a file synching service like DropBox) in the most secure and compact format, IOK files. And because this data is usually very sensitive, they will be password protecting their submitted IOK files.

I have re-classified this as an idea

I voted for the idea to put user/password to open protected IOK file which contains sensitive data :D

Had this yet been implemented or when can we expect this by?

This has now been implemented in 2.8, available in the next few weeks.

An optional field "Password" will appear in File actions, allowing you to specify a password needed to open an IOK file for processing. The file will keep the password if your action subsequently saves it, unless you set a new password using Secure File. It's not possible to remove, only change, a password via Secure File.

Until 2.8, you must store working IOK files for the Scheduler without passwords, somewhere secure on your Server installation.