Repository navigation
Conversation
Invoke-IDRestMethod decodes exp from the WebSession's Authorization header when a request returns 401. An expired token reports the expiry time and directs the user to New-IDSession or New-IDPlatformToken; every other 401 is unchanged.
Replace any paging key already in the caller's URI rather than appending a second one, keeping other query keys byte for byte. Advance offsets from the starting offset in the URI or POST body instead of from zero.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Changed
Session expired at <time>: authenticate again with New-IDSession or New-IDPlatformToken. Previously, it reportedUnauthorized. Unauthorized..Companion modules get the same message.
Fixed
Each later request carries one offset or cursor, in place of the starting one, and pages on from the
starting offset. Previously, the starting value was sent again with each later request, and paging
restarted from zero, so items were skipped or returned twice.
Fixes #
Type of change
How Has This Been Tested?
Checklist: