Remove old appliction clients via an API?

[Joshua Brown]

Hi,

In my quest to automate standing up and tearing down GCS instances, I'm running into a few issues. Currently, one of the problems that I am hitting when trying to create idempotent commands is when I try to cleanup an endpoint, it looks like the gcs application credentials still show up in the web UI after the endpoint has been cleaned up.

sudo globus-connect-server endpoint cleanup -c $CLIENT_ID -y

To remove them I am having to manually log in to the Globus developer UI and delete them. Is there a pathway for automating removal of the GCS client?

best, 

JB

[Jason Alt]

Automatic cleanup of the endpoint's client credentials when running 'endpoint cleanup' is on our list of features we plan to include. Note that doing so will cause the command to become interactive since the operation requires user credentials in order to access the Globus Auth API. The non-interactive path will be to use client credentials with the GCS CLI operations and assign the client as a project admin on the Auth project that contains the endpoint's credentials.

In the meantime, I believe you can use the Globus CLI with client credentials (see https://docs.globus.org/cli/environment_variables/#client_credentials_with_globus_cli_client_id) to delete the endpoint client from the Auth project. See https://docs.globus.org/api/auth/reference/#delete_client and make use of the 'globus api auth delete' subcommand.  

Jason