Welcome to the WSO2 Identity Server source code! For info on working with the WSO2 Identity Server repository and contributing code, click the link below.
When trying federated SMS OTP flow in latest and IS 7.0, getting the following runtime exception. Note that this occurs only when the mobile number is not configured for the user.
[db2352f9-fec5-4c6c-92dd-4dd27a53617f] ERROR {org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/].[bridgeservlet]} - Servlet.service() for servlet [bridgeservlet] in context with path [/] threw exception [Servlet execution threw an exception] with root cause java.lang.ClassNotFoundException: org.wso2.carbon.identity.central.log.mgt.utils.LoggerUtils cannot be found by org.wso2.carbon.extension.identity.authenticator.smsotp.connector_3.3.20
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:512)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:423)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:415)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:155)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at org.wso2.carbon.identity.authenticator.smsotp.SMSOTPAuthenticator.getMobileNumberRequestPage(SMSOTPAuthenticator.java:441)
at org.wso2.carbon.identity.authenticator.smsotp.SMSOTPAuthenticator.redirectToMobileNoReqPage(SMSOTPAuthenticator.java:1067)
at org.wso2.carbon.identity.authenticator.smsotp.SMSOTPAuthenticator.getMobileNumber(SMSOTPAuthenticator.java:375)
at org.wso2.carbon.identity.authenticator.smsotp.SMSOTPAuthenticator.initiateAuthenticationRequest(SMSOTPAuthenticator.java:317)
at org.wso2.carbon.identity.authenticator.smsotp.SMSOTPAuthenticator.process(SMSOTPAuthenticator.java:192)
at org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler.doAuthentication(DefaultStepHandler.java:725)
How to reproduce:
Setup federated SMS OTP authenticator. Use the management console with the identity providers feature enabled.
Add the configured federated SMS OTP as the second factor to an application.
Create a user. Do not configure the mobile number for the user.
Try login to the application and select configured SMS OTP as the second factor.
Application will crash with above exception in server logs.
Expected behavior:
Mobile number configuring page should be rendered.
Environment information (Please complete the following information; remove any unnecessary fields) :
Describe the issue:
When trying federated SMS OTP flow in latest and IS 7.0, getting the following runtime exception. Note that this occurs only when the mobile number is not configured for the user.
How to reproduce:
Expected behavior:
Mobile number configuring page should be rendered.
Environment information (Please complete the following information; remove any unnecessary fields) :