Skip to content

Conversation

@aseigler
Copy link
Contributor

Revoke access token, then set token to null.

Alias Invoke-OktaRemoveAccessToken for backward compatibility.

Minor fix to Invoke-OktaApiClient, skip call to DeserializeResponse if RawResponse.Content is empty, which it is with successful token revocation.

Resolves #66.

Revoke access token, then set token to null.
Alias Invoke-OktaRemoveAccessToken for backward compatibility.
Minor fix to Invoke-OktaApiClient, skip call to DeserializeResponse if RawResponse.Content is empty, which it is with successful token revocation.
@laura-rodriguez
Copy link
Contributor

laura-rodriguez commented Dec 19, 2024

Thank you so much for your contribution @aseigler. We'll review your PR thoroughly as soon as possible based on the team's priorities. In the meantime, can you please review and sign the Okta CLA?

Once the CLA has been signed and we confirm the functionality is OK, we'll have to port your changes to the codegen templates. Ideally, we would love to have some unit tests, so feel free to add a few if that's available to you. Otherwise, the team will take of it.

Internal Ref: OKTA-847057

@laura-rodriguez
Copy link
Contributor

@aseigler Thank you for your patience.

Your PR has been included in #79, and it's waiting for review. Thank you again for your contribution!

laura-rodriguez added a commit that referenced this pull request Feb 13, 2025
Test and verify "Implement Invoke-OktaRevokeAccessToken" (#67)
@laura-rodriguez
Copy link
Contributor

Superseded by #79

@aseigler aseigler deleted the feat-revoketokens branch February 13, 2025 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invoke-OktaRemoveAccessToken should revoke the access token prior to nulling it out

2 participants