@Jovack, I’m a bit late to the party here, but I think you might be laboring under the same misunderstanding that I had about access tokens. You say that you want to get “a list of the associated auth tokens for each core.”
Unfortunately an access token is associated with an account rather than with a particular core – so having an access token for your account means someone can access any of your cores rather than just one particular core.
Even more unfortunately, access tokens are very nearly “the keys to the kingdom” – having an access token allows you to not only read from your cores or call functions on them, but also to flash your cores, claim new cores to your account, release cores from your account…just about anything except managing access tokens.
It sounds like you – like me – want to have some way of granting access to the variables and functions exposed by a particular core rather than giving away everything. I’ve been hacking on the spark-cli tool for a couple of days to familiarize myself with it and make sure I understand access tokens, and I’ll probably be starting a thread in this category soon proposing a new kind of token/key that will let us have finer control over these things.