Aug 10 09:39:07.838 DBG arguments: [--verbosity, debug, -p, XXX, auth, activate-service-account, --service-account-key-path, service_account_key.json]
Aug 10 09:39:07.838 DBG configuration is persisted and read from: XXX
Aug 10 09:39:07.838 DBG read configuration profile "default" via
Aug 10 09:39:07.838 DBG active configuration profile: default
Aug 10 09:39:07.839 DBG configuration keys: [allowed_url_domain: stackit.cloud, assume_yes: false, async: false, project_id: XXX, region: eu01, session_time_limit: 2h, verbosity: debug]
Aug 10 09:39:07.839 DBG parsed input values: [OnlyPrintAccessToken: false, ServiceAccountKeyPath: service_account_key_new.json]
Aug 10 09:39:07.847 DBG authenticating using service account key
Aug 10 09:39:08.064 ERR get access token: get new access token: , status code 400, Body: {"error":"invalid_grant","error_description":"JWT signature validation failed."}
Aug 10 09:39:08.064 ERR execute command: could not setup authentication based on the provided service account credentials.
Please double check if they are correctly configured.
For more details run:
$ stackit auth activate-service-account -h
Error: could not setup authentication based on the provided service account credentials.
Please double check if they are correctly configured.
For more details run:
$ stackit auth activate-service-account -h
Description
When creating a new key via the CLI, the key is unusable unless you remove
.credentials.tokenEndpoint.Steps to reproduce
Actual behavior
Expected behavior
Login should work without removing
.credentials.tokenEndpoint.Environment