Solved!
Go to SolutionR
ritu86jain
1 Rookie
•
32 Posts
0
6233
December 14th, 2017 06:00
ScaleIO Login API error
Hi there,
I am using following api to login to ScaleIO version 2.0.13000.211 - /api/login
But instead of returning the authentication key, it returns "certificate not trusted"
{"message":"","httpStatusCode":428,"errorCode":0,"certificate":{"Serial Number":"1","Subject":"OU=ASD, O=EMC, C=US, ST=Massachusetts, L=Hopkinton, CN=ScaleIO-123-123-123-123, GIVENNAME=MDM","Signature Algorithm":"SHA1withRSA","Signature":"[B@5fbb1d1a","Issuer":"OU=ASD, O=EMC, C=US, ST=Massachusetts, L=Hopkinton, CN=ScaleIO-123-123-123-123, GIVENNAME=MDM","Valid-From":"Wed Nov 29 17:46:03 UTC 2017","Valid-To":"Sun Nov 28 18:46:03 UTC 2027","Key-Usage":"Not Available","Public Key":"[B@512953b3","Thumbprint Algorithm":"SHA-1","Thumbprint":"c4 0b 34 rt 61 e4 bc 2a 01 81 a5 0b 41 9a 5b 05 fd cd 76 0e "},"typeOfError":"SERVER_CERTIFICATE_NOT_TRUSTED"}
What does this mean and how can it be fixed? Does this mean that API is not supported?
Thank you,
RItu
PS. Information changed in response.
ritu86jain
1 Rookie
•
32 Posts
5250
0
Posted December 14th, 2017 07:00
Thank you for a quick response dstratton
Where can we find "localhost_access_log.log" ? This is customers environment, so it may take some time to try above things.
please try to login to the IM Web GUI and connect to the MDM from the Maintain Tab.
If displays a certificate warning, you should be able to add it to the gateway's keystore.
Im wondering what the "localhost_access_log.log" shows
can we try the CURL command below?
curl -k -v --basic --user admin: https:// /api/login
Im also wondering if when you try the CURL command using the gateway with which you installed the ScaleIO system,
if your able to get a key(token) in the HTTP response.
basically seen this in an instance from https://community.emc.com/message/992052?et=watches.email.thread#992052
Hi,
I'm using ScaleIO 3.0 and stuck with this stupid HTTP 428 reply. Nothing helped.
I read and read documentation and then tried https:// /api/gatewayLogin and it worked, it returned the token!
So documentation is misleading. Use 'gatewayLogin' instead of 'login' at the end of URL !
andyinv
37 Posts
5250
0
Posted December 14th, 2017 07:00
two options: one is to use the insecure option for CURL
-k, --insecure (SSL) This option explicitly allows curl to perform "insecure" SSL connections and transfers. All SSL connections are attempted to be made secure by using the CA certificate bundle installed by default. This makes all connections considered "insecure" fail unless -k, --insecure is used.
The other is to get a properly signed and trusted certificate (preferably with your own PKI) into ScaleIO, so you can trust it.