GetFactorType() returning IllegalArgumentException about okta-sdk-java HOT 10 CLOSED

@kiranbud I'll reach out to internal teams to see if this is missed in documentation.

from okta-sdk-java.

12.0.0 is released with the fix.

from okta-sdk-java.

Thanks for posting!

Are you really using 1.5.2 SDK version as noted in the issue description?

Can you please upgrade to the latest version and try this please (1.5.2 version is retired)?

from okta-sdk-java.

I had the same issue with v10.x. The fix for this specific issue is quite easy, I did this in my fork:
https://github.com/okta/okta-sdk-java/compare/master...clementdenis:okta-sdk-java:signed_nonce?expand=1

However, the schema for the UserFactor corresponding to factorType=signed_nonce is probably incorrect, so I did not submit a PR for this.

from okta-sdk-java.

signed_nonce is not a defined/documented factor type per https://developer.okta.com/docs/reference/api/factors/#factor-type. In the spec, we usually add the documented factor types only.

Did you try with the latest SDK version 10.3.0? I am unable to reproduce the issue with 10.3.0 myself.

For the user in question, what are all the factors you had enrolled the user into (programmatically/UI)?

from okta-sdk-java.

Yes, unfortunately we are using 1.5.2
We decided to upgrade but that is going to take sometime as we have to test so many cases.
We enrolled in SMS (Okta), Phone, Push (Okta) factors. But not sure how this signed_nonce factor is coming up by default. I also see token:software:totp coming up by default but this is present in the factor-type list.

from okta-sdk-java.

Internal Ref: This is dependent on OKTA-611365. Once the doc update goes public, the SDK will then be updated.

from okta-sdk-java.

PR #903 will fix this.

from okta-sdk-java.

PR merged to master, next release will be cut soon.

from okta-sdk-java.

Thank you @arvindkrishnakumar-okta

from okta-sdk-java.