After updating WSO2 IS using U2 I can see the following intermittent debug log when I try to log in to my SP.
TID: [-1234] [] [2022-12-05 22:13:30,322] [bcc826e3-5dcf-4a14-8048-6fd6b59d4599] DEBUG {org.wso2.carbon.identity.application.authentication.framework.AbstractApplicationAuthenticator} - Error occurred during the authentication process, hence retrying. org.wso2.carbon.identity.application.authentication.framework.exception.InvalidCredentialsException: User authentication failed due to invalid credentials
...
at org.wso2.carbon.identity.application.authenticator.basicauth.BasicAuthenticator.processAuthenticationResponse(BasicAuthenticator.java:699)
at org.wso2.carbon.identity.application.authentication.framework.AbstractApplicationAuthenticator.process(AbstractApplicationAuthenticator.java:89)
at org.wso2.carbon.identity.application.authenticator.basicauth.BasicAuthenticator.process(BasicAuthenticator.java:141)
at org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler.doAuthentication(DefaultStepHandler.java:512)
at org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler.handleResponse(DefaultStepHandler.java:486)
at org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler.handle(DefaultStepHandler.java:180)
at org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler.handle(DefaultStepBasedSequenceHandler.java:186)
at org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.GraphBasedSequenceHandler.handle(GraphBasedSequenceHandler.java:113)
at org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultAuthenticationRequestHandler.handle(DefaultAuthenticationRequestHandler.java:159)
at org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator.handle(DefaultRequestCoordinator.java:249)
at org.wso2.carbon.identity.application.authentication.framework.servlet.CommonAuthenticationServlet.doPost(CommonAuthenticationServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:681)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
...
And I cannot proceed to my SP in the browser.
How can I fix this?
The above issue can happen if you have updated the IS using either WUM or U2 tools. If you open the network tracer of the application via your browser, you can see there is an error when loading the jQuery library. This is the root cause of this intermittent error.
To solve this, you should replace every .jsp file (residing in the <IS_HOME>/repository/deployment/server/webapps directory) containing the
<script type="text/javascript" src="libs/jquery_3.4.1/jquery-3.4.1.js"></script> with
<script type="text/javascript" src="libs/jquery_3.6.0/jquery-3.6.0.js"></script>
which is the new version of your jQuery library in the IS.
Currently, the above issue is occurring with jQuery 3.4.1 and it can be fixed with replacing the script tags related to jQuery loading. But if the jQuery version changes, you have to find the exact jQuery version by going through the webapps.
Related
I have used github-pages to publish my site. I'm trying to use onesignal there. But I can't store the sdk files in the root. I'm getting this console error.
Installing service worker failed TypeError: Failed to register a ServiceWorker for scope ('https://username.github.io/') with script ('https://username.github.io/OneSignalSDKWorker.js?appId=<MY_APP_ID>'): A bad HTTP response code (404) was received when fetching the script.
A 404 means the service worker script is not where the SDK thinks it is. Try visiting the URL in your browser (https://username.github.io/OneSignalSDKWorker.js). You should see the script there. If it is not there, you have not successfully hosted the required file.
I recently upgraded Visual Studio 2017 to version 15.5.0 and later on to 15.5.1.
So far everything was working fine developing .NET Core (2.0) web apis but after the updates the problems started. The problems occur on existing projects as well as newly created ones.
Problems:
Sometimes I receive the error message:
Unable to start process C:\Program Files\dotnet\dotnet.exe. The web server request failed with status code 500, Internal Server Error. The full response has written to C:\Users\username\AppData\Local\Temp\HttpFailure_04-01-08.html
This hidden directory is a great place to store error files by the way.
If i look into that file I can read:
HTTP Error 500.19 - Internal Server Error
Module: IIS Web Core
Notification: Begin Request
Error Code: 0x800700b7
Configuration file: \?\C:\solution\project\web.config
configuration source
<handler>
<add name="aspNetCore" path="*" verb="*" module="AspNetCoreModule" resourceType="Unspecified" />
</handler>
It seems to automatically add the add-tag on start even when I delete it.
So far, deleting the .vs directory up and on seemed to help against this but this shouldn't be a permanent solution.
The second (and more blocking problem) that occured is that the APP URL setting seems to be broken somehow.
For testing this bug I created a new Web API project (with the values controller) and added and configured swashbuckle.AspNetCore to show the UI for the ValuesController.
The default route for the values controller is api/values.
When I now configure the App URL settings in the project properties to start at http://localhost:50000/swagger the browser opens and shows the wrong url, namely http://localhost:50000/swagger/api/values with the correct response of the ValuesController but not the swagger ui. At this point it shouldn't have the extension /api/values since it is not configured and I don't know why or where this is added (it's not in the configuration).
If I now enter (without stopping the app) http://localhost:50000/swagger I start receiving 404 errors an urls, even on http://localhost:50000/api/values.
Anyone else having this problem?
Anyone knows a fix for that?
Anyone knowing what is happening there and what the problem could be?
I am trying to implement a database integration on a system that triggers, after a user creation, a account creation on Zimbra service through ZimbraAdminService.
The server version is 8.6
On Pentaho Web Service Lookup step, when I fill the URL field with https://example.com/service/wsdl/ZimbraAdminService.wsdl and hit "Load" button, I get the following error:
Could not load WSDL file: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'zimbra.xsd'.: java.io.FileNotFoundException: This file was not found: file:/C:/Program Files/Pentaho/data-integration/zimbra.xsd
I already checked the documentation on https://wiki.zimbra.com/wiki/Wsdl
Anyone faced such problem and has a solution? Thanks.
To solve the problem above, I had to go to the browser, access the following addresses, load and save the XML generated of the xsd services as .xsd extension:
https://example.com/service/wsdl/zimbra.xsd
https://example.com/service/wsdl/zimbraAdmin.xsd
https://example.com/service/wsdl/zimbraAdminExt.xsd
https://example.com/service/wsdl/zimbraMail.xsd
https://example.com/service/wsdl/zimbraRepl.xsd
https://example.com/service/wsdl/zimbraSync.xsd
https://example.com/service/wsdl/zimbraVoice.xsd
Put this files on /your-program-install-folder/Pentaho/data-integration (on Windows - C:\Program Files\Pentaho\data-integration)
After doing that, the problem will be solved.
I'm getting blank pages when navigating the WSO2 ESB-4.9.0 management console. For example, the registry, templates, endpoints, and local entries pages are all blank when navigating to them in the console UI.
I've found the following errors in the logs:
Error during rendering
IO Error executing tag: JSPException while including path '/templates/list_templates.jsp'. ServletException while including page.
The ESB is running in a YAJSW Windows Service. I should note that the ESB runs fine when running straight from the command line, it's just when using the service wrapper.
Strainy
Since you mentioned that the ESB starts as a window service, in carbon 4.4.x, default wrapper.conf file needs to be updated with following additional entries.
wrapper.java.additional.26 = -Dwso2.carbon.xml=${carbon_home}\\repository\\conf\\carbon.xml
wrapper.java.additional.27 = -Dwso2.registry.xml=${carbon_home}\\repository\\conf\\registry.xml
wrapper.java.additional.28 = -Dwso2.user.mgt.xml=${carbon_home}\\repository\\conf\\user-mgt.xml
wrapper.java.additional.29 = -Dwso2.transports.xml=${carbon_home}\\repository\\conf\\mgt-transports.xml
wrapper.java.additional.31 = -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
wrapper.java.additional.33 = -Dfile.encoding=UTF8
You can verify these configurations in wrapper.conf and these configurations may help you to solve the jsp error.
Following link may help you if you need more information regarding this.
https://docs.wso2.com/display/ESB490/Installing+as+a+Windows+Service#InstallingasaWindowsService-SettinguptheYAJSWwrapperconfigurationfile
I just used the NSSM - the "Non-Sucking Service Manager".
It's actually amazingly simple to install a Service using this tool.
https://nssm.cc
Just set it up to point at the wso2server.bat file
Keeping an eye on this issue however: https://wso2.org/jira/browse/ESBJAVA-4342
I am using Jetty server with embedded web app. However, whenever I hit any resource which is not present it serves a default page which shows a message "Powered by Jetty".
This page is being served from org.eclipse.jetty.server.handler.DefaultHandler.handle.
I want write a custom handler for this, however while trying to register custom Handler in jetty.xml file, I am getting syntax exception and server doesn't start anymore.
I was able to resolve this issue by doing some tweaks along with changes mentioned in Deactivate Jetty's default 404 error handler.