Ask a Question

Failed to import a definition / no subject alternative names matching

prometheus
Occasional Contributor

Failed to import a definition / no subject alternative names matching

Hi  all

 

It shows "Failed to import a definition" when I import the url from readyAPI 3.10

or "smartbear javax.net.ssl.SSLHandshakeException no subject alternative names matching"

and shows "could not import a definition from the specified file" when I import the url from readyAPI 3.3

 

This RESTAPI communicate with clients via HTTPS protocol. Exchange data format is json.

This URL looks like this:  https://[ip]:[port]/[Rest_Resource]

 

I checked the proxy setting of ReadyAPI is on(automatic)

 

 

5 REPLIES 5
richie
Community Hero

Re: Failed to import a definition / no subject alternative names matching

Hey @prometheus,

Im a little confused could you add in some further info to clarify please?

It sounds like youre trying to load in a definition file like a swagger/wadl/OAS. Is this correct?

You mention v3.10 but you also mention v3.3. Could you clarify what you meant by this?

You mention that youve checked and the proxy setting is set to true, but is this required by the endpoint youre trying to hit? Whether you are proxying your requests would be determined by your technical requirements. Should you be using a proxy?

SSL handshake/socket exceptions are pretty low level stuff, and this stuff needs to be set correctly before worrying about authentication/authorisation and payload wellformed/valid considerations. When ive had SSL/socket exceptions before it's something very fundamental thats been required to fix....like TLS/SSL versioning or incorrecr use of HTTP/HTTPS. What i mean is, i thought it was HTTPS when in fact the endpoint was expecting no secure HTTP. Have you checked this?

Cheers,

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
prometheus
Occasional Contributor

Re: Failed to import a definition / no subject alternative names matching

Hey @richie 

 

The Application developer told me it's a free form of REST API, didn't use swagger/wadl.

 

I just updated our testing tool, and  there are two shortcuts on my desktop, one is for ReadyAPI 3.3 and another one is for ReadyAPI 3.10.

 

The technical requirement didn't mention the proxy.

I google and found some people with similar issues mentioned the proxy.

 

After some digging, I found it's probably a very fundamental stuff. 

Because it's HTTPS connection, so the certificate authentication is required.

I am going to try if I could store the self-signed certificate to the keystore for mutual authentication and reply to this thread later

 

 

 

 

richie
Community Hero

Re: Failed to import a definition / no subject alternative names matching

Hey @prometheus,

Oh god yeah...if certs are required then without them that'd likely cause an SSL exception. Sorry you didnt mention certs otherwise i wouldve latched onto that as the probable cause

Nice one

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
sonya_m
Community Manager

Re: Failed to import a definition / no subject alternative names matching

Thank you so much, Richie!

 

@prometheus how did it go? Please let the Community know if you still need help🙂


Sonya Mihaljova
Community and Education Specialist

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
prometheus
Occasional Contributor

Re: Failed to import a definition / no subject alternative names matching

@richie just let you know, I tried self signed certificate and transformed it to a pfx format, load it into the file > preference > SSL setting > keystore

But it's still the same.

 

I escalate the issue to the support team, and she said it's due to the specific structure used in API definition which not fully supported by ReadyAPI yet.

 

We are still working on it.

 

Thanks

 

cancel
Showing results for 
Search instead for 
Did you mean: