We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description Command for creating obo token returns error
Reproduction databricks token-management create-obo-token {service_principal_id} Using workspace profile: prod
Expected behavior I expect a token from the referenced service principal.
Is it a regression? I don't know.
Debug Logs Request log:
POST /api/2.0/token-management/on-behalf-of/tokens > * Host: > * Accept: application/json > * Authorization: REDACTED > * Content-Type: application/json > * User-Agent: cli/0.219.0 databricks-sdk-go/0.39.0 go/1.21.9 os/linux cmd/token-management_create-obo-token auth/pat > { > "application_id": "fb58f866-62b3-4e08-8f3f-c599db43ffe2" > } < HTTP/2.0 403 Forbidden < * Content-Length: 52 < * Content-Type: application/json; charset=utf-8 < * Date: Tue, 24 Sep 2024 18:31:26 GMT < * Server: databricks < * Vary: Accept-Encoding < * X-Databricks-Reason-Phrase: Invalid access token. < * X-Request-Id: acf159a1-5fb8-4e71-8ddb-38bd87f81393 < { < "error_code": 403, < "message": "Invalid access token." < }
Other Information
Additional context The prior obo token started failing before we got this issue.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
Command for creating obo token returns error
Reproduction
databricks token-management create-obo-token {service_principal_id}
Using workspace profile: prod
Expected behavior
I expect a token from the referenced service principal.
Is it a regression?
I don't know.
Debug Logs
Request log:
Other Information
Additional context
The prior obo token started failing before we got this issue.
The text was updated successfully, but these errors were encountered: