Subscribe

Ontap API for HTTPS on 9.0

[ Edited ]

 

ApiRunner ontapiRunner = new ApiRunner(ApiTarget.builder().withHost(host).withPort(port).withUserName(username).withPassword(password).withTargetType(TargetType.FILER).useProtocol(Protocol.HTTP).build());

 

What are minimal configuration requirements to talk to the OntapApi using HTTPS for ONTAP 9.0?  The above code works IF I enabled the http option using the advanced settings.

 

If I disable the http option, and change to Protocol.HTTPS or Protocol.INSECURE_HTTPS, I get connection refused.  However, if i re-rename the http option and use either of the HTTPS options in the API I get Unrecognized SSL message, plaintext connection?

 

Re: Ontap API for HTTPS on 9.0

Hello,


I had a similar issue and I end up debugging NetApp Python library to find in which line it makes the connection to filer. Maybe you need that to.


I've just wrote the following post about that:

 

http://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Tricks-to-work-with-self-signed-certificate-over-TLS-on-python-sdk-5-6...

 

Re: Ontap API for HTTPS on 9.0

This may have nothing to do with your situation, but I noticed the other day that ONTAP 9.0 seems to require a working reverse DNS PTR record in DNS (for cluster_mgmt). Those are normally in place but if accidentally omitted, ONTAP 8.3.2 let you get away with, ONTAP 9.0 does not. This may be part of TLS, I don't know.

Re: Ontap API for HTTPS on 9.0

This is not because TLS. If I'm not wrong this is related to internal DNS configuration.

https://kb.netapp.com/support/s/article/ka31A00000012CGQAY/how-to-set-up-dns-load-balancing-in-clustered-data-ontap?language=en_US