Closed charlie-gallagher closed 2 years ago
For what it's worth, I include a description of the JSON file fields in ?aw_auth
Regarding the json file format that is downloaded from inside the developer.adobe console: The json file is downloaded and looks like this -->
Preferably we would not require the end-user to edit this file in any way and simply make another argument that would identify where the private.key file is located.
Perfect, thank you! I'll use this as the reference
@benrwoodard is API_KEY the same as CLIENT_ID? I don't see CLIENT_ID in the json
Yes
I changed things around slightly:
AW_AUTH_FILE
and AW_PRIVATE_KEY
?aw_auth
@charlie-gallagher One quick question. I have a situation right now where the client will not give me the JSON file but has given me all the variables needed. Have you already described a way of manually creating the JSON file for auth?
Hey @benrwoodard I took a couple minutes to convert JWT authentication from the crude environment variable approach (all my fault...) to this much nicer file-based approach. It functions the same as with
googleanalyticsr
, like we discussed.IMPORTANT: I wasn't the one who downloaded/generated our json file containing our authentication info -- I just inherited it. Do you know if it's possible to download the credentials, or do we need to clarify how to format the JSON file as well?
AW_AUTH_FILE
contains the file path to the authentication JSONfile
argument toaw_auth
.aw_auth
documentation as well. I am on my way to updating the readme documentation.Example:
Checklist:
devtools::document()