Could not find com.duosecurity:DuoWeb:1.3.
cantor.2 at osu.edu
Mon Jan 24 16:37:23 UTC 2022
As previously announced on the dev list, we are no longer providing access to any third party artifacts. Our own builds are still in process of being adjusted to use Maven Central while we iron out the signature verification machinery, but they're strictly internal now.
Duo does not, as it happens, put their artifacts in Maven Central (and we don't blame them). But it's still third party. I don't think we intended to make an exception for those cases but I'll bring it up.
Assuming it's not removed outright in time, V5 will probably move the old Duo code to a plugin so that it isn't part of the core build.
More information about the users