- Issue created by @rajeshreeputra
- @rajeshreeputra opened merge request.
- 🇮🇳India rajeshreeputra Pune
Created MR with following:
- Add key module in dev dependency
- Update configuration form allowing to use the Key module to get api key and shared secret.
- Manually created a simple authentication key using file key provider and used in config form for key based authentication.
- Added new
getCredentials()
to retrieve API key and shared secret from keyValue or config as per key module used. - Verified connection is successful with key module as well as with config.
How to use key module with Acquia SEO Content Insights:
- Require and install key module.
- Create new key with file key provider or any other, I am using the file key provider to create the
Conductor credentials
key. - Add required details to file, i.e. api_key and shared_secret as json.
- Visit
/admin/config/development/conductor
:- You will see a new checkbox option(Use Key module for API credentials storage) under the API Credentials.
- Check the checkbox option.
- The API Key dropdown field will appear, allowing you to select the key from the list.
- Choose the
Conductor credentials
key. - Click on Save configurations.
- You will receive a success or error message based on the data in the file path provided in the key.
Remaining work:
- Update Acquia SEO Content Insights extention to support key module integration.
- Verified the functionality.
- Add test coverage for key module integration.