Cool @danbroudy! I like the supplier approach, as the json file contains both the identity and credential.
I'd only change the name of the supplier so it reflects it is for the json file format, and assume a json string as an input (as we do with the PEM string in the default auth) and delegate the file read to users. This way we don't get coupled to how the json file is stored. Makes sense? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/124#issuecomment-71804916
