WSO2 IS配置SMS OTP后点击发送OTP出现405错误求助

我正在实现双因素认证流程：第一步要求用户输入用户名和密码，第二步通过SMS OTP完成验证。但配置好SMS OTP后，点击「发送OTP按钮」时触发了405错误。

405错误页面地址：

https://localhost:9443/smsotpauthenticationendpoint/smsotp.jsp?client_id=fJsj8UV4QEH5yWkuLjevFruYGyMa&commonAuthCallerPath=%2Foauth2%2Fauthorize&forceAuth=false&passiveAuth=false&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2Fpickup-dispatch%2Foauth2client&response_type=code&scope=openid+internal_application_mgt_view&tenantDomain=carbon.super&sessionDataKey=cc73a6e6-168d-40ce-8003-c0c2a26afa16&relyingParty=fJsj8UV4QEH5yWkuLjevFruYGyMa&type=oidc&sp=pickup-dispatch&isSaaSApp=false&multiOptionURI=%2Fauthenticationendpoint%2Foauth2_login.do%3Fauthenticators%3DEmailOTP%253AGmail%2BOTP%253BSMSOTP%253ASMS%2BOTP%253Btotp%253ALOCAL%26response_type%3Dcode%26type%3Doidc%26tenantDomain%3Dcarbon.super%26client_id%3DfJsj8UV4QEH5yWkuLjevFruYGyMa%26relyingParty%3DfJsj8UV4QEH5yWkuLjevFruYGyMa%26passiveAuth%3Dfalse%26isSaaSApp%3Dfalse%26commonAuthCallerPath%3D%252Foauth2%252Fauthorize%26scope%3Dopenid%2Binternal_application_mgt_view%26forceAuth%3Dfalse%26sessionDataKey%3Dcc73a6e6-168d-40ce-8003-c0c2a26afa16%26redirect_uri%3Dhttp%253A%252F%252Flocalhost%253A8080%252Fpickup-dispatch%252Foauth2client%26sp%3Dpickup-dispatch&authenticators=SMSOTP

我已修改部署文件，添加了以下配置：

### SMS CONFIGURATION ###
[authentication.authenticator.sms_otp] 
name ="SMSOTP"
enable=true

[authentication.authenticator.sms_otp.parameters]
SMSOTPAuthenticationEndpointURL= "/smsotpauthenticationendpoint/smsotp.jsp"
SMSOTPAuthenticationEndpointErrorPage= "/smsotpauthenticationendpoint/smsotpError.jsp"
MobileNumberRegPage = "/smsotpauthenticationendpoint/mobile.jsp"
RetryEnable = true
ResendEnable = true
BackupCode = true
SMSOTPEnableByUserClaim = true
usecase = "local"
secondaryUserstore = "primary"
SMSOTPMandatory = true
SendOtpToFederatedMobile = false
federatedMobileAttributeKey = "mobile"
CaptureAndUpdateMobileNumber = true
SendOTPDirectlyToMobile = false
redirectToMultiOptionPageOnFailure = false
TokenExpiryTime = 12

我的短信服务商要求使用GET请求，但官方文档中所有短信服务商示例都采用POST方式，这会不会是导致405错误的原因？

短信身份提供者配置截图：

内容的提问来源于stack exchange，提问作者Mugisha Solomon Bekunda