perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Casey,

Currently there is no command to explicitly set the API key. There’s a couple way around this which may or may not apply. If you are migrating to a new esmond instance, if you migrate the data over your old API keys will come with it so you shouldn't have to change anything. See http://docs.perfsonar.net/multi_ma_backups.html#migrating-data. In particular if all you care about is the API keys you could just do the PostgreSQL steps listed.

Another way around this is to use IP authentication for your hosts instead of API keys. See http://docs.perfsonar.net/multi_ma_install.html#authenticating-by-ip-address.

Thanks,

Andy

On September 27, 2017 at 4:14:02 PM, Casey Russell () wrote:

Group,

     Is there a modification to these commands: 

python esmond/manage.py add_ps_metadata_post_user example_user

python esmond/manage.py add_timeseries_post_user example_user

or a separate command to specify an API key for a user (as opposed to having the local instance create one).  I'm migrating from an old machine to a new and thought it would be nice to modify this API key on the new esmond MA instead of going out and modifying it in config files on 8+ testing hosts.

I'd like to set the API key for my "mesh_user" on this new MA to be the same as the API key on the old MA

Sincerely,

Casey Russell

Network Engineer

785-856-9809

2029 Becker Drive, Suite 282
Lawrence, Kansas 66047