Repository navigation
docs: SK-3253: Document automatic retry on 401 for expired bearer tokens - #450
promptless[bot] wants to merge 2 commits into
Conversation
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
|
Semgrep Findings: Issues with Error level severity are found (Error is Highest severity in Semgrep), Please resolve the issues before merging. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #450 +/- ##
============================================
+ Coverage 91.00% 91.04% +0.04%
- Complexity 0 545 +545
============================================
Files 174 174
Lines 7350 7350
Branches 1013 1013
============================================
+ Hits 6689 6692 +3
+ Misses 437 435 -2
+ Partials 224 223 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep Findings: Issues with Error level severity are found (Error is Highest severity in Semgrep), Please resolve the issues before merging. |
Open in Promptless
Documents the automatic one-time retry on
401for expired SDK-generated bearer tokens, added in #449 (SK-3253). That PR merged intoflowvault-release/26.10.28; publish this tomainalongside or after that release reachesmain.Why
401when the token is at or within 60 seconds of expiry.setTokentokens.Goal
skyvault/README.md: rewrites "Bearer token expiry edge case" to describe the automatic retry and when it applies, and to keep manual handling for connection calls andsetToken. Replaces the detokenize retry example with a connection-call retry and fixes its sample link to theskyvault/samplespath.skyvault/samples/.../BearerTokenExpiryExample.java: updated to match the README example.flowvault/README.md: adds "Bearer token expiry during a call" under Authenticate, including how the retry relates totimeoutandmaxRetries, what happens to the remaining batches when token generation fails, plus a TOC entry.docs/api_reference.md: adds the new publicToken.isExpiringWithin(String, long)method.Testing
BaseVaultClient,Token, bothVaultClientclasses, andConnectionClientat the merged PR headd82f4f1d, including the follow-up change that stops retrying a token whose regeneration already failed..cspell.json. The sample wasn't compiled; it uses the same APIs as the existingInvokeConnectionExample.Trigger Events