Change for Authors Using FTP

Hi everyone, Just letting you know we’re going to be deploying a change that means authors using FTP will only be able to login (to FTP) using their API key (currently it’s password OR API key).

When the change goes out, we’ve changed the FTP program to say; “login incorrect. Passwords are no longer accepted to authenticate via FTP, please use your API key instead. You can read more about the API here.

FAQs
Do I have generate my API key first? Yes you’ll have to generate one, you can find how how here.

What happens if I revoke that one and then re-generate another? If you revoke an API key then you will have to update the FTP program with an active API key

What if they have multiple API Keys? You can use any of your active API keys.

I just curious and don’t know technical consideration behind this. Is it more more confidential password than API? Because we only use password to access Envato’s site, and sometimes we easily give our API key to any 3rd party, such as application even that is not Envato’s official.

Jakartanese said
I just curious and don’t know technical consideration behind this. Is it more more confidential password than API? Because we only use password to access Envato’s site, and sometimes we easily give our API key to any 3rd party, such as application even that is not Envato’s official.

At this time of the year may i suggest that a message is placed on authors dashboards or send out an email as many will not see this message and you will then receive a flood of posts no doubt in the new year asking why their FTP uploads are not working.

Just a suggestion.

Jonathan

Jakartanese said
I just curious and don’t know technical consideration behind this. Is it more more confidential password than API? Because we only use password to access Envato’s site, and sometimes we easily give our API key to any 3rd party, such as application even that is not Envato’s official.

Even with this change I think it’s still ok. Because even if someone used your API key + ftp, all they can really do is upload something to your account storage. They’d still have to have your password to apply that to an official upload/update.

+1 for Jonathan’s suggestion.

billyf said
In that case, you should generate a new API key which is meant specifically for your FTP only

CodingJack said
Even with this change I think it’s still ok. Because even if someone used your API key + ftp, all they can really do is upload something to your account storage. They’d still have to have your password to apply that to an official upload/update.

Yes, never think about that, haha. Thank you billyf & CodingJack.

Thanks for this information

Thx for the info

billyf said

Jakartanese said
I just curious and don’t know technical consideration behind this. Is it more more confidential password than API? Because we only use password to access Envato’s site, and sometimes we easily give our API key to any 3rd party, such as application even that is not Envato’s official.

In that case, you should generate a new API key which is meant specifically for your FTP only

It actually doesn’t matter, because they said any API key can be used to log in into ftp accout

But, on the other hand, CodingJack is right, the only bad thing that can happen is that somebody logs into your ftp account and uploads something to it. They can’t download anything, nor can they do anything with the uploaded files afterwards. But still, I wouldn’t like somebody messing with my ftp account.