Bluemix: bms-samples-android-helloauthentication error - ibm-cloud

I'm trying to run sample BMS app for Google based authorization
https://github.com/ibm-bluemix-mobile-services/bms-samples-android-helloauthentication
It runs on Android Studio emulator after changing targetSdkVersion to 22 in build.gradle (I've got java.lang.SecurityException: Missing android.permission.GET_ACCOUNTS before the change)
I've got following error on my physical device after pressing "Ping Bluemix" button:
02-25 12:32:49.446 30033-31086/com.ibm.helloauthentication E/mfpsdk.AuthorizationProcessManager: AuthorizationProcessManager.handleAuthorizationFailure in AuthorizationProcessManager.java:426 :: authorization process failed
02-25 12:32:49.446 30033-31096/com.ibm.helloauthentication W/System.err: at com.android.org.conscrypt.OpenSSLX509Certificate.checkValidity(OpenSSLX509Certificate.java:216)
02-25 12:32:49.446 30033-31096/com.ibm.helloauthentication W/System.err: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.certificate.CertificatesUtility.checkValidityWithPublicKey(CertificatesUtility.java:59)
02-25 12:32:49.446 30033-31096/com.ibm.helloauthentication W/System.err: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.AuthorizationProcessManager.saveCertificateFromResponse(AuthorizationProcessManager.java:214)
02-25 12:32:49.446 30033-31096/com.ibm.helloauthentication W/System.err: ... 12 more
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: Get request to Bluemix failed: THROWNjava.lang.RuntimeException: Failed to save certificate from response
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.AuthorizationProcessManager.saveCertificateFromResponse(AuthorizationProcessManager.java:222)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.AuthorizationProcessManager.access$100(AuthorizationProcessManager.java:51)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.AuthorizationProcessManager$1.handleAuthorizationSuccessResponse(AuthorizationProcessManager.java:133)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.AuthorizationProcessManager$InnerAuthorizationResponseListener.onSuccess(AuthorizationProcessManager.java:469)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.AuthorizationRequestAgent.processResponse(AuthorizationRequestAgent.java:388)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.AuthorizationRequestAgent.processResponseWrapper(AuthorizationRequestAgent.java:542)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.ibm.mobilefirstplatform.clientsdk.android.security.internal.AuthorizationRequestAgent.onSuccess(AuthorizationRequestAgent.java:513)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.ibm.mobilefirstplatform.clientsdk.android.core.api.internal.BaseRequest$1.onResponse(BaseRequest.java:419)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.squareup.okhttp.Call$AsyncCall.execute(Call.java:170)
02-25 12:32:49.451 30033-31096/com.ibm.helloauthentication E/MainActivity: at com.squareup.okhttp.internal.NamedRunnable.run(NamedRunnable.java:33)
Any ideas?


Updated that sample to use the correct permissions handling so you should be able to run it at SDK 23+ assuming you grant the permission when prompted.
I am still unable to recreate your specific issue on a physical device, but for this type of failure I would suggest first verifying that a bad header hasn't been cached (resolved by uninstalling and reinstalling the application) and should that fail I would recommend removing the certificate from Bluemix and re-adding it to reset the permissions and grants associated with it.

Related

Why won't my deployment group agent connect to the server?

I'm trying to provision a deployment group agent (vsts-agent-win-x64-2.170.1.zip) on a lab machine for an on-premises DevOps server. The registration script successfully completes, the VstsAgentAService runs, and I can see the agent in the deployment group (the machine is present and all the Capabilities are visible) but it appears Offline.
Even though the script was clearly able to communicate with the server to provide the Capabilities, things break down when it's the agent's turn.
Event Viewer (VstsAgentAService):
2022-05-16 18:19:32Z: Agent connect error: An error occurred while sending the request.. Retrying until reconnected.
_diag log:
[2022-05-16 18:15:59Z INFO VisualStudioServices] Starting operation Location.GetConnectionData
[2022-05-16 18:15:59Z WARN VisualStudioServices] Attempt 1 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:15:59Z WARN VisualStudioServices] Attempt 1 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:15:59Z WARN VisualStudioServices] Attempt 1 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:16:10Z WARN VisualStudioServices] Attempt 2 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:16:10Z WARN VisualStudioServices] Attempt 2 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:16:10Z WARN VisualStudioServices] Attempt 2 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:16:23Z WARN VisualStudioServices] Attempt 3 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:16:23Z WARN VisualStudioServices] Attempt 3 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:16:24Z WARN VisualStudioServices] Attempt 3 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The operation will be retried[...]
[2022-05-16 18:16:40Z ERR VisualStudioServices] Attempt 4 of GET request to https://[url] failed (WinHttp Error: ERROR_WINHTTP_SECURE_FAILURE). The maximum number of attempts has been reached.
[2022-05-16 18:16:40Z INFO VisualStudioServices] Finished operation Location.GetConnectionData
[2022-05-16 18:16:40Z INFO AgentServer] Catch exception during connect. 4 attempt left.
[2022-05-16 18:16:40Z ERR AgentServer] System.Net.Http.HttpRequestException: An error occurred while sending the request.
---> System.Net.Http.WinHttpException (80072F8F, 12175): Error 12175 calling WINHTTP_CALLBACK_STATUS_REQUEST_ERROR, 'A security error occurred'.
This is when I run the registration script with authentication type: negotiate. If I instead run the script using PAT, it fails right off the bat.
config.cmd:
Enter authentication type (press enter for PAT) >
Enter personal access token > ****************************************************
Error reported in diagnostic logs. Please examine the log for more details.
- C:\dev\azagent\_diag\Agent_20220516-174740-utc.log
TF400813: Resource not available for anonymous access. Client authentication required.
_diag log:
[2022-05-16 17:55:48Z WARN VisualStudioServices] Basic issued token provider instance 52136803 requires an interactive prompt which is not allowed by the current settings
[2022-05-16 17:55:48Z ERR VisualStudioServices] GET request to https://[url] is not authorized. Details: VS30063: You are not authorized to access https://[url].
[2022-05-16 17:55:48Z INFO VisualStudioServices] Finished operation Location.GetConnectionData
[2022-05-16 17:55:48Z INFO LocationServer] Catch exception during connect. 4 attempt left.
[2022-05-16 17:55:48Z ERR LocationServer] Microsoft.VisualStudio.Services.Common.VssUnauthorizedException: VS30063: You are not authorized to access https://[url].
If I go to the URL with Chrome (and enter my credentials), it dumps a bunch of "authenticatedUser" information. Clearly the server is happy with my credentials.
Does anyone know what's going on? What am I missing to make the sever recognize the agent beyond the initial registration?

SOAP Service Error: org.xmlpull.v1.XmlPullParserException: expected: START_TAG {http://schemas.xmlsoap.org/soap/envelope/}Envelope

I just migrated my soap service from old server to new server and starts getting this error. Soap service is deployed on IIS. I have checked the WSDL on both servers and they are same.
W/System.err: org.xmlpull.v1.XmlPullParserException: expected: START_TAG {http://schemas.xmlsoap.org/soap/envelope/}Envelope (position:START_TAG <html>#1:7 in java.io.InputStreamReader#d6c3cee)
W/System.err: at org.kxml2.io.KXmlParser.require(KXmlParser.java:2125)
at org.ksoap2.SoapEnvelope.parse(SoapEnvelope.java:128)
at org.ksoap2.transport.Transport.parseResponse(Transport.java:129)
W/System.err: at org.ksoap2.transport.HttpTransportSE.parseResponse(HttpTransportSE.java:304)
at org.ksoap2.transport.HttpTransportSE.call(HttpTransportSE.java:276)
at org.ksoap2.transport.HttpTransportSE.call(HttpTransportSE.java:118)
at com.prodserver.tfandroid.services.soap.TFService.getUserLogin(TFService.java:255)
at com.prodserver.tfandroid.ui.activity.LoginActivity$LoginAsyncTask.doInBackground(LoginActivity.java:234)
W/System.err: at com.prodserver.tfandroid.ui.activity.LoginActivity$LoginAsyncTask.doInBackground(LoginActivity.java:214)
at android.os.AsyncTask$2.call(AsyncTask.java:333)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:245)
W/System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)

Unable to get push token. Getting error: 907135004, EXECUTE_TIMEOUT

I was able to get the token for push couple hours ago. After I reinstalled the application, I couldn't get the push token anymore and was getting error EXECUTE_TIMEOUT. According to HMS documentation, it suggested me to contact customer service. I'm unable to get registration token multiple times and don't know what is causing this to happen. My application code for getting the push token never changed, it worked before but not now.
Here is the log:
2021-05-10 15:37:45.969 29250-30669/com.myapp.push I/HMSSDK_PendingResultImpl: setResult:0
2021-05-10 15:37:45.973 29250-29250/com.myapp.push I/HMSSDK_BaseAdapter: baseCallBack.onComplete
2021-05-10 15:37:45.975 29250-29250/com.myapp.push I/HMSSDK_HmsClient: receive msg status_code:0, error_code907135004, api_name:push.gettoken, app_id:100000000|, pkg_name:com.myapp.push, session_id:*, transaction_id:100000000ttoken20210510153735889477123, resolution:null
2021-05-10 15:37:45.976 29250-29250/com.myapp.push E/HMSSDK_HmsInstanceIdEx: TokenTask failed, ErrorCode: 907135004
2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: com.huawei.hms.common.ApiException: 907135004: execute timeout
2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.opendevice.a.a(ErrorEnum.java:272)
2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.opendevice.i.doExecute(GetTokenTask.java:58)
2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.opendevice.i.doExecute(GetTokenTask.java:34)
2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.common.internal.TaskApiCall.onResponse(TaskApiCall.java:190)
2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.common.internal.HuaweiApiManager$ConnectionManager$1.onCallback(HuaweiApiManager.java:272)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.common.internal.HmsClient$a.a(HmsClient.java:100)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.common.internal.HmsClient$a.onComplete(HmsClient.java:122)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.adapter.BaseAdapter$BaseRequestResultCallback.a(BaseAdapter.java:277)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.adapter.BaseAdapter$BaseRequestResultCallback.onResult(BaseAdapter.java:252)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.adapter.BaseAdapter$BaseRequestResultCallback.onResult(BaseAdapter.java:175)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.support.api.PendingResultImpl$a.b(PendingResultImpl.java:490)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.support.api.PendingResultImpl$a.handleMessage(PendingResultImpl.java:467)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at android.os.Handler.dispatchMessage(Handler.java:110)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at android.os.Looper.loop(Looper.java:219)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at android.app.ActivityThread.main(ActivityThread.java:8387)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at java.lang.reflect.Method.invoke(Native Method)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513)
2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1055)
2021-05-10 15:37:45.975 29250-29250/com.myapp.push I/HMSSDK_HmsClient: receive msg status_code:0, error_code907135004, api_name:push.gettoken, app_id:100000000|, pkg_name:com.myapp.push, session_id:*, transaction_id:100000000ttoken20210510153735889477123, resolution:null 2021-05-10 15:37:45.976 29250-29250/com.myapp.push E/HMSSDK_HmsInstanceIdEx: TokenTask failed, ErrorCode: 907135004 2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: com.huawei.hms.common.ApiException: 907135004: execute timeout 2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.opendevice.a.a(ErrorEnum.java:272) 2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.opendevice.i.doExecute(GetTokenTask.java:58) 2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.opendevice.i.doExecute(GetTokenTask.java:34) 2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.common.internal.TaskApiCall.onResponse(TaskApiCall.java:190) 2021-05-10 15:37:45.978 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.common.internal.HuaweiApiManager$ConnectionManager$1.onCallback(HuaweiApiManager.java:272) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.common.internal.HmsClient$a.a(HmsClient.java:100) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.common.internal.HmsClient$a.onComplete(HmsClient.java:122) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.adapter.BaseAdapter$BaseRequestResultCallback.a(BaseAdapter.java:277) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.adapter.BaseAdapter$BaseRequestResultCallback.onResult(BaseAdapter.java:252) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.adapter.BaseAdapter$BaseRequestResultCallback.onResult(BaseAdapter.java:175) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.support.api.PendingResultImpl$a.b(PendingResultImpl.java:490) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.huawei.hms.support.api.PendingResultImpl$a.handleMessage(PendingResultImpl.java:467) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at android.os.Handler.dispatchMessage(Handler.java:110) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at android.os.Looper.loop(Looper.java:219) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at android.app.ActivityThread.main(ActivityThread.java:8387) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at java.lang.reflect.Method.invoke(Native Method) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513) 2021-05-10 15:37:45.979 29250-30477/com.myapp.push W/System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1055)

This error code suggests that AIDL has a call timed out. Please try the steps as below:
Check whether your phone has internet access, verify that the network connection is stable and the notification function is enabled on the device.
Clear the app cache, HMS Core (APK) cache and restart the device.
Please verify that the token on the device is correct. You can send a message to the device from the console of AppGallery Connect. If the message was sent from the console but you still cannot receive it on the phone, the token has expired or the device configuration is incorrect. Please check the token and configure device permissions. If the message is successfully sent and received, we can conclude that the API parameters are set incorrectly.
Please check the format of the message body encapsulated on the server. You are advised to check the message body fields by referring to Sending Downlink Messages.

Problem with Jboss EAP 7 server.log and application log

i have the following problem with jboss log and my application log. Some errors are write in server log in this way
15:46:16,834 ERROR [io.undertow.request] (default task-41) UT005023: Exception handling request to /fnsuap/cmd/home: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:982)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
....
And then are write in my application log in this way:
[09/06/20 03:46:15:015 CEST] ERROR stderr: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds
[09/06/20 03:46:15:015 CEST] ERROR stderr: at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:982)
[09/06/20 03:46:15:015 CEST] ERROR stderr: at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
[09/06/20 03:46:15:015 CEST] ERROR stderr: at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
[09/06/20 03:46:15:015 CEST] ERROR stderr: at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
[09/06/20 03:46:15:015 CEST] ERROR stderr: at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
[09/06/20 03:46:15:015 CEST] ERROR stderr: at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
[09/06/20 03:46:15:015 CEST] ERROR stderr: at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
...
So is like every line of stacktrace is a new error.
Why this happens? How can i solve this?
Use log4j1.2

java.security.KeyStoreException: java.security.NoSuchAlgorithmException: KeyStore jks implementation not found

In my application i am using xmpp and openfir for chat. Chat is working fine but in log i am getting below exception. I googled it I couldn't find an answer. Where should i implement jks
05-25 12:59:27.245 25643-26419/com.it.example D/SMACK: 12:59:27 PM SENT (161744330): <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
05-25 12:59:27.365 25643-26419/com.it.example D/SMACK: 12:59:27 PM RCV (161744330):
05-25 12:59:27.365 25643-26419/com.it.example W/System.err: java.security.KeyStoreException: java.security.NoSuchAlgorithmException: KeyStore jks implementation not found
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at java.security.KeyStore.getInstance(KeyStore.java:119)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at org.jivesoftware.smack.ServerTrustManager.(ServerTrustManager.java:71)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at org.jivesoftware.smack.XMPPConnection.proceedTLSReceived(XMPPConnection.java:858)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:250)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:46)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:72)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: Caused by: java.security.NoSuchAlgorithmException: KeyStore jks implementation not found
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at org.apache.harmony.security.fortress.Engine.notFound(Engine.java:190)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at org.apache.harmony.security.fortress.Engine.getInstance(Engine.java:139)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: at java.security.KeyStore.getInstance(KeyStore.java:116)
05-25 12:59:27.375 25643-26419/com.it.example W/System.err: ... 5 more