Skip to Main Content

Application Development Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Weblogic applicaiton as secure webservice client (HTTPS)

2736471Aug 20 2014 — edited Aug 20 2014

Hi,

I am facing a issue while calling a secure(https) webservice from my application deployed in weblogic 10.0.

javax.xml.ws.soap.SOAPFaultException: T9WSC  Certificate missing or invalid (owner)

        at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:160)

        at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:83)

        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:248)

        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:212)

        at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:105)

Using same keystore I am able to make call webservice using standalone Java program. I have set this keystore as Identity and trust keystore and mention alias name in SSL configuration.  I have also set below mention java parameter to same keystore file.

javax.net.ssl.keyStore

javax.net.ssl.keyStorePassword

javax.net.ssl.trustStore

javax.net.ssl.trustStorePassword

Here is SSL debug statement before this error occured:

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 0>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 0>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (0): NONE>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Performing hostname validation checks: y008.defbs.ffts.com>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: CertificateRequest>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHelloDone>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <No suitable identity certificate chain has been found.>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 7>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacMD5>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacMD5>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm SHA>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.5 for algorithm RC4>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacMD5>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacMD5>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.5 for algorithm RSA>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 134>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <write CHANGE_CIPHER_SPEC, offset = 0, length = 1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.5 for algorithm RC4>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HMACSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HMACSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacMD5>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacMD5>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 16>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <10294441 SSL3/TLS MAC>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <10294441 received CHANGE_CIPHER_SPEC>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.5 for algorithm RC4>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HMACSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HMACSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <10294441 SSL3/TLS MAC>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <10294441 received HANDSHAKE>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Finished>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacMD5>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacMD5>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.5 for algorithm HmacSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacSHA1>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <write APPLICATION_DATA, offset = 0, length = 306>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <write APPLICATION_DATA, offset = 0, length = 339>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <7972330 read(offset=0, length=8192)>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <10294441 SSL3/TLS MAC>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <10294441 received APPLICATION_DATA: databufferLen 0, contentLength 643>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <7972330 read databufferLen 643>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <7972330 read A returns 643>

<20.08.2014 16.46 Uhr CEST> <Debug> <SecuritySSL> <BEA-000000> <avalable(): 7972330 : 0 + 0 = 0>

Comments

fac586
Answer

Hi Scott
The checkboxes are a feature that is enabled when Page Designer is used on a device with a touch-based UI. This is therefore likely to be related to the switch to iPad emulation. Check that all of the relevant browser options have been reset, but you may need to shut down the entire browser session and clear the site data.

Marked as Answer by Scott Wesley · Sep 6 2021
Scott Wesley

That makes sense, thanks.
I couldn't find a relevant setting, but a restart of the browser did the job.

McRivers

Just stumbled across this in 21.2. Thought I was going crazy "those checkboxes haven't 'always' been there, right?" i was saying to myself. ;)
@fac586 appreciate the solution...

Scott Wesley

Based on information from Magaly Iraheta on Twitter, and combining that with what I new I did, I can now recreate and “fix ”this on demand, with no need for browser restart.

If you enable mobile emulation (toggle device toolbar) with the developer tools, then click anywhere in the application builder, the key APEX.userHasTouched appears in Application-Session Storage.

On refresh of the builder page, these checkboxes will appear.

If you delete this key, then refresh the page, the checkboxes will no longer be present.

Thanks again, Magaly.

1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 17 2014
Added on Aug 20 2014
0 comments
111 views