search

contentstack / contentstack-export

Node.js utility to export content from Contentstack
MIT License
7 stars 13 forks source link

Deprecated Access Tokens: support for Delivery and Management Tokens #31

Open morancj opened 4 years ago

morancj commented 4 years ago

Hi, According to ContentStack docs Home > Developers > Create Tokens > Types Of Tokens #Access Tokens, ContentStack have

deprecated Access Tokens for all stacks, and we will soon stop supporting it. We recommend using Delivery Tokens to access published content and Management Tokens for making content management API requests.

This repo makes use of both the Content Management API and Content Delivery API endpoints., as well as the Image Delivery API endpoint. I can't see which tokens are supported by the image delivery API endpoint.

config/index.js refers only to access and management tokens: do you have any plans to extend it to support delivery and management tokens? access_token is used liberally in this repo.

ninadhatkar commented 4 years ago

Thanks, @morancj for reaching out to us.

We will be soon updating the script by removing access_token before it is deprecated and use the alternatives of delivery and management tokens wherever required.

morancj commented 4 years ago

Thank @ninadhatkar , please close when done. :) When working on this, I kindly ask you to please double-check the use of token names in variables, so it's consistent and matches the documentation on https://www.contentstack.com/docs/developers/.

morancj commented 4 years ago

Hi @ninadhatkar, @rohitmishra209, any news on this?

morancj commented 4 years ago

Hi @ninadhatkar, @rohitmishra209, according to this email from ContentStack:

From: Contentstack info@contentstack.com Date: Mon, 31 Aug 2020 at 21:00 Subject: Deprecation of Access Tokens (August 30, 2020)

Stacks created after our September 30, 2020, will no longer see Access Tokens in the Stacks menu. All existing Access tokens will remain valid while they’re in use. Going forward, Delivery Tokens should be used to fetch all published content and Management Tokens for fetching unpublished content or using the Content Management API.

As mentioned, we will continue to support Access Tokens for older stacks, however, we highly recommend moving to Delivery and Management tokens for all stacks.

Should we need to recreate our Access Tokens (for example, due to staffing changes), our website build will fail, so this is very important to us.

morancj commented 4 years ago

Support told me to use the management_token until this package is updated. Lines 53-59 of login.js seem to describe this: https://github.com/contentstack/contentstack-export/blob/9429cddae37fa0f8f800c356e1e547c6aeb58cc6/lib/util/login.js#L53-L59 If I only set source_stack & management_token, I can export again, thanks. This still needs documenting and updating though. :)

rohitmishra209 commented 4 years ago

Hi @morancj Thanks for reaching out to us. We will have a meeting with doc teams on this and update it soon

imeugenia commented 3 years ago

Hello,

Do you have any estimated time when the deprecated access_token will be removed from this project? We would like to use this tool but run into error 'Kindly provide access_token or api_token'.