The access will be revoked permanently for this API key, encryption phrase and path. This means that if you created a new access grant with the same exact options as the already revoked one had, it will not work either since this access grant configuration was already revoked.
Therefore, to create a new access grant again for the same object, you need to use either a different API key, different encryption phrase, different path, or different access options.
For example, as workaround to ¨restore¨ a previously revoked access, you could use the
--not-before flag in the
share command to specify some time in the past (
--not-before -1m for example) to create a new access grant for the same path with the same API key and the same encryption phrase but with a different access option.
uplink share --not-before -1m sj://cakes/cheesecake.jpg
This command will create an access with option - do not allow access earlier than one minute in the past - however it will not affect the ability to access an object, because this restriction is already satisfied, but the access grant will be effectively different from the initial one that had been revoked.