Reasons for use_duo_code_attribute about duo_universal_java HOT 6 CLOSED

@philsmart This capability was added in commit ca089b0 and we'll soon be releasing 1.1 to include it. Thanks for using Duo and let us know if this does not address your concern.

from duo_universal_java.

Hi, thanks for the question. There were some issues we found with third-party libraries used within thick clients that inappropriately used the code parameter. This caused our implementation to break. We are investigating a long term solution but in the meantime we introduced duo_code as a temporary workaround. Please feel free to use the code attribute as it typically works for any non-thick client use case.

from duo_universal_java.

Many thanks, as long as there are no security implications, I can work with it.

from duo_universal_java.

There does not appear to be a way to revert to the old behavior with the universal-sdk - use_duo_code_attribute is hard coded to true. Is there a plan to allow this to be toggled on or off.

from duo_universal_java.

Just wondering if there was any update on the above?

from duo_universal_java.

Thanks for bringing this up. You're right, we currently are hard coding use_duo_code_attribute to be true. We are tracking this issue internally.

from duo_universal_java.