Uses of Class
com.okta.sdk.resource.model.ResendUserFactor
-
Uses of ResendUserFactor in com.okta.sdk.resource.api
Modifier and TypeMethodDescriptionUserFactorApi.resendEnrollFactor
(String userId, String factorId, ResendUserFactor resendUserFactor, String templateId) Resend a Factor enrollment Resends an `sms`, `call`, or `email` factor challenge as part of an enrollment flow For `call` and `sms` factors, Okta enforces a rate limit of one OTP challenge per device every 30 seconds.UserFactorApi.resendEnrollFactor
(String userId, String factorId, ResendUserFactor resendUserFactor, String templateId, Map<String, String> additionalHeaders) Resend a Factor enrollment Resends an `sms`, `call`, or `email` factor challenge as part of an enrollment flow For `call` and `sms` factors, Okta enforces a rate limit of one OTP challenge per device every 30 seconds.Modifier and TypeMethodDescriptionUserFactorApi.resendEnrollFactor
(String userId, String factorId, ResendUserFactor resendUserFactor, String templateId) Resend a Factor enrollment Resends an `sms`, `call`, or `email` factor challenge as part of an enrollment flow For `call` and `sms` factors, Okta enforces a rate limit of one OTP challenge per device every 30 seconds.UserFactorApi.resendEnrollFactor
(String userId, String factorId, ResendUserFactor resendUserFactor, String templateId, Map<String, String> additionalHeaders) Resend a Factor enrollment Resends an `sms`, `call`, or `email` factor challenge as part of an enrollment flow For `call` and `sms` factors, Okta enforces a rate limit of one OTP challenge per device every 30 seconds. -
Uses of ResendUserFactor in com.okta.sdk.resource.model
Modifier and TypeMethodDescriptionResendUserFactor.factorType
(ResendUserFactor.FactorTypeEnum factorType)