Closed 3sRykaert closed 10 months ago
Hi @3sRykaert,
We're not planning to add convenience methods to parse links in the near future. What you could potentially do is either mimic what we did in 5.x and adding a partial class with a GetTransactionId()
or add a helper that parses links.
For this particular case, you have to do the following to get the transaction ID:
var transactionId = verifyUserFactorResponse.Links.Poll.Href.Split('/').Last();
Describe the feature request?
Hey @laura-rodriguez ,
now that #671 and #672 are merged to the "release branch", is there a easier solution possible then manually parsing the "VerifyUserFactorResponse.Links.Poll.Href" to get the transactionId from the response? Now I have to "manually" parse the following result:
In Okta.SDK 5.x there was this functionality (but was removed in v6.x), see f.e.: https://github.com/okta/okta-sdk-dotnet/blob/v5.6.2/src/Okta.Sdk/VerifyUserFactorResponse.cs
New or Affected Resource(s)
okta-sdk-dotnet
Provide a documentation link
https://developer.okta.com/docs/reference/api/factors/#issue-a-push-factor-challenge
Additional Information?
507