Deactivate Admin API Key

OttoFMS
1

I have a use case where I need to use OttoDeploy hosted and managed by the client and do an Install/Replace to my dev server.

I do not however want to leave my Admin API key available in the OttoDeploy since the client shouldn’t have access to it.

Right now, I am creating a new API key each time and deleting it after use.

Is there a way to instead simply deactivate the API key on my dev server, so I don’t need to go in and change it in the client’s OttoDeploy each time?

2

Hey David,

There is no way to deactivate an Admin API key without deleting it. Do you trigger the Install/Replace or do they?

My recommendation would be to simply retrigger from OttoFMS instead of adding and deleting an admin api key every time. The key is only used to kick off the deployment, so you could do the following without having to worry about access:

  1. create an admin api key and add it to their ottodeploy
  2. kick off the deployment to your dev server
  3. delete the admin api key
  4. the next time you need to run the deployment, just rerun it from the ottofms console.
  5. Repeat step 4 ad infinitum
  6. If you ever need to change the deployment settings, you could repeat steps 1-3 again.

Does that fit your use case?

-Kyle

3

Hi Kyle,

Thanks Kyle, that’s actually a great idea. I’ve just gotten so used to running the deployments from OttoDeploy, but doing it from /otto/app/deployments is of course even easier.

/David

1 Like