- 
                Notifications
    
You must be signed in to change notification settings  - Fork 332
 
Description
I'm trying to use the behance importer (jekyll-import behance --user NAME --api_token TOKEN) to import my projects into my Jekyll site, as described in the documentation.
However, I'm encountering a significant problem obtaining the required --api_token. When following the standard process of going to the Adobe Developer Console to generate API credentials:
- There doesn't appear to be a direct option to "Add API" specifically for "Behance" anymore.
 - The available APIs (like various Creative Cloud APIs) and authentication methods (often OAuth 2.0 or Service Account JWT) do not seem to provide a simple, persistent API Key/Token that matches the format expected by the 
--api_tokenparameter of this script. The console workflows appear geared towards more complex application integrations. 
This suggests that the simple API key authentication method the jekyll-import behance tool relies upon may have been deprecated or changed by Adobe/Behance. As a result, it seems difficult or impossible for a user to generate the necessary credential to use this importer currently.
Could you please provide some guidance or clarification on this?
- Is there a known, current method to obtain a compatible API token for the Behance importer?
 - Does the importer perhaps need to be updated to support newer Adobe/Behance authentication methods?
 - Or is the Behance importer currently non-functional due to these upstream API access changes?
 
Any information or update would be greatly appreciated. Thank you for maintaining this useful tool!