Invalid Auth Token when auth token is expired after 12h
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 技術堆疊
- python
- 領域
- api, authentication
研究方向
從 cloudfoundry_client/client.py 開始，特別查看 init_with_client_credentials 路徑以及第 271 行和第 309 行的請求處理，然後將行為與 pull request #88 進行比較。在 token 過期後重現 v3 請求；完成的標準是，過期 token 情境不再產生回報的 unauthorized failure。
由索引模型根據 Issue 內容生成。
描述
Hi,
we are using cloudfoundry-client==1.30.0.
Our code is part of a servicebroker with the openbrokerapi framework.
We are trying to access the cf api with a client_id and a client_secret.
Our code is as follows in the constructor:
self._client = CloudFoundryClient(url, verify=cacert_path, client_id=client_id, client_secret=client_secret)
self._client.init_with_client_credentials()
to access one result we later use:
app_guid_response = self._client.v3.apps.get(app_guid)
If the login with init_with_client_credentials() is more than 12h ago, the token expires and accessing the api fails with:
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [OUT] {"message": "GET: url=https://our.cf.api/v3/service_credential_bindings/9f103727-baab-464f-887e-f28d084119c0 - status_code=401 - vcap-request-id=e395a697-22ba-495c-9213-1667df377148::edc717be-bcd4-4f8a-b8eb-65ded1283297 - response={\n \"errors\": [\n {\n \"detail\": \"Invalid Auth Token\",\n \"title\": \"CF-InvalidAuthToken\",\n \"code\": 1000\n }\n ]\n}", "time": "2022-08-18T06:20:42.746518"}
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] DEBUG:cloudfoundry_client.client:GET: url=https://our.cf.api/v3/service_credential_bindings/9f103727-baab-464f-887e-f28d084119c0 - status_code=401 - vcap-request-id=e395a697-22ba-495c-9213-1667df377148::edc717be-bcd4-4f8a-b8eb-65ded1283297 - response={
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] "errors": [
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] {
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] "detail": "Invalid Auth Token",
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] "title": "CF-InvalidAuthToken",
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] "code": 1000
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] }
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] ]
2022-08-18T08:20:42.746+02:00 [APP/PROC/WEB/0] [ERR] }
The stacktrace is part of some more elements, here are the parts from cloudfoundry-client:
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] service_binding_response = self._client.v3.service_credential_bindings.get(service_binding_guid)
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] File "/home/vcap/deps/0/python/lib/python3.8/site-packages/cloudfoundry_client/v3/entities.py", line 238, in get
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] return self._get(requested_path, **kwargs)
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] File "/home/vcap/deps/0/python/lib/python3.8/site-packages/cloudfoundry_client/v3/entities.py", line 133, in _get
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] response = self.client.get(url_requested)
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] File "/home/vcap/deps/0/python/lib/python3.8/site-packages/cloudfoundry_client/client.py", line 271, in get
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] return CloudFoundryClient._check_response(response)
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] File "/home/vcap/deps/0/python/lib/python3.8/site-packages/cloudfoundry_client/client.py", line 309, in _check_response
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] raise InvalidStatusCode(HTTPStatus(response.status_code), body, response.headers.get("x-vcap-request-id"))
2022-08-18T08:20:42.751+02:00 [APP/PROC/WEB/0] [ERR] cloudfoundry_client.errors.InvalidStatusCode: UNAUTHORIZED = {"errors": [{"detail": "Invalid Auth Token", "title": "CF-InvalidAuthToken", "code": 1000}]} - vcap-request-id = e395a697-22ba-495c-9213-1667df377148::edc717be-bcd4-4f8a-b8eb-65ded1283297
I thought https://github.com/cloudfoundry-community/cf-python-client/pull/88 was supposed to fix that problem?
Thanks!
- Lorenz
- 主要語言
- Python
- 星號
- 55
- 分支
- 54
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
cloudfoundry-community/cf-python-client 的其他 Issue
-
難度 3/5 1-2 天 新手友好度 45/100
cloudfoundry-community/cf-python-client#218 · 3 則留言 ·
-
難度 4/5 3-5 天 新手友好度 25/100
-
難度 4/5 3-5 天 新手友好度 35/100
-
難度 4/5 3-5 天 新手友好度 35/100
cloudfoundry-community/cf-python-client#180 · 2 則留言 ·
-
難度 4/5 3-5 天 新手友好度 30/100
cloudfoundry-community/cf-python-client#170 · 2 則留言 ·
查看 cloudfoundry-community/cf-python-client 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 68/100
jbacalso24/mimry#291 ·
維護者通常 1 天內回覆
-
good first issue
難度 2/5 1 小時以內 新手友好度 82/100
eli-alvarado/us-watchlist-alerts#14 ·
維護者通常 1 天內回覆
-
from-review-extraction python severity:nit
難度 2/5 1-3 小時 新手友好度 80/100
LearningCircuit/local-deep-research#7462 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
cathrynlavery/diagram-design#441 ·
維護者通常 2 天內回覆
-
[Cleanup] Include the public header in work_split.cpp可能已有人在做 @blozano-tt 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 82/100
tenstorrent/tt-metal#60850 ·
維護者通常 1 天內回覆