10-16-2024 07:12 AM - edited 10-16-2024 09:27 AM
In my Global Policy, I have an Operating system setting:
Allow Android devices:
Encourage users to update if less than the latest.
Encourage to update: after 30 days.
Block versions: if less than the latest.
Block: after 60 days.
The problem I'm having is that my users started getting Version Restricted blocked today if they were running Android 14. My question is: What does Duo consider the release date for Android 15? What is 30/60 days after that? 60 days before today was August 17, 2024 which doesn't sound right for Android 15.
Solved! Go to Solution.
10-16-2024 11:05 AM
Quick response from Support. Posting it here in case anyone else is searching the forums...
Hi Kevin,
Thanks for reaching out to Duo Security Support. I understand that you have set up your Android OS policy such that users are blocked after 60 days if not running the latest Android OS. However, Android 15 was released yesterday, and users on lower versions are already being blocked. I can absolutely assist with this!
I brought this information up to our product team, and we discovered a mistake in the policy logic that was resulting in a much earlier release date being used when determining allowed Android OS versions. We have now corrected this, such that October 15th is considered the Android 15 release date. This change should have kicked in already, but may take up to an hour to fully propagate through our systems.
Thank you for sharing your experience with us and helping us to identify this issue! Let me know if I can clarify or expand upon any of the above information.
Best regards,
Blake
10-16-2024 11:05 AM
Quick response from Support. Posting it here in case anyone else is searching the forums...
Hi Kevin,
Thanks for reaching out to Duo Security Support. I understand that you have set up your Android OS policy such that users are blocked after 60 days if not running the latest Android OS. However, Android 15 was released yesterday, and users on lower versions are already being blocked. I can absolutely assist with this!
I brought this information up to our product team, and we discovered a mistake in the policy logic that was resulting in a much earlier release date being used when determining allowed Android OS versions. We have now corrected this, such that October 15th is considered the Android 15 release date. This change should have kicked in already, but may take up to an hour to fully propagate through our systems.
Thank you for sharing your experience with us and helping us to identify this issue! Let me know if I can clarify or expand upon any of the above information.
Best regards,
Blake
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide