
7oz7j (7oz7j) asked a question.
Consider the current flow:
- An SMS factor is enrolled via the Enroll Okta SMS Factor API method. The phone number is 123
- This factor is subsequently activated via the Acivate SMS Factor API method.
- Then we deactivate the factor using the Reset Factor API method.
When we then repeat the steps from 1 with the same phone number (123), the factor is enrolled and auto-activated. This means that there's no SMS received by the phone and no challenge.
---
Is this expected behaviour, and if so, is there a way we can always force it to send a new SMS on the enrolment even if it's the same number? I've tried using the query param 'updatePhone=true' but it also makes no difference.

Hi, @7oz7j (7oz7j)
Thank you for posting on our Community page!
I have done some research and found this article that might give you a clearer insight into your issue:
https://developer.okta.com/docs/reference/api/factors/#enroll-okta-sms-factor-by-using-existing-phone-number
In short, yes, it is expected behaviour. You can raise a feature request on ideas.okta.com for our Engineering team to take into account.
Thank you for reaching out to our Community and have a great day!
_____________________________________________________________________________
The October issue of the Okta Community is here and packed with tips on certification, how to earn badges, and new releases. Let us help you stay connected.
_____________________________________________________________________________
If my answer helped, remember to select it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
_____________________________________________________________________________