This post is more than 5 years old
5 Posts
0
2718
Cannot Authenticate Against ScaleIO Gateway Any Longer
Greetings,
Environment:
ScaleIO 2.0-6035.0
The environment is fully deployed. I can authenticate against MDM using traditional "admin" and password, no problem:
ScaleIO-192-168-120-151:~/install # scli --login --mdm_ip 192.168.120.150 --username admin --password XXXXXXXXX
Logged in. User role is SuperUser. System ID is 076534e45e5ed7ca
ScaleIO-10-60-120-151:~/install # scli --mdm_ip 192.168.120.150 --sdc --query_all_sdc
MDM restricted SDC mode: Disabled
Query all SDC returned 15 SDC nodes.
SDC ID: d503826c0000000e Name: N/A IP: 192.168.120.165 State: Disconnected GUID: 99222D6D-0BED-4DAA-994E-D76D7CD25F08 Version: N/A
Read bandwidth: 0 IOPS 0 Bytes per-second
Write bandwidth: 0 IOPS 0 Bytes per-second
SDC ID: d503826b0000000d Name: N/A IP: 192.168.120.163 State: Disconnected GUID: 28A19C7E-636A-4020-A674-5796BC341D8B Version: N/A
Read bandwidth: 0 IOPS 0 Bytes per-second
Write bandwidth: 0 IOPS 0 Bytes per-second
SDC ID: d503826a0000000c Name: N/A IP: 192.168.120.161 State: Disconnected GUID: FC3602E2-B3A2-4D5B-B6AA-721E1603C51D Version: N/A
Read bandwidth: 0 IOPS 0 Bytes per-second
Write bandwidth: 0 IOPS 0 Bytes per-second
...
My REX-Ray was working fine as well, authenticating against my ScaleIO Gateway, but now, it is failing to authenticate.
[root@mslave4 rexray]# curl -k --user admin:XXXXXX https://192.168.120.166/api
{
"message" : "Unauthorized",
"httpStatusCode" : 401,
"errorCode" : 0
}[root@node4 rexray]#
Any clues on how to tackle the problem?? Why would it stop authenticating ?
Thanks,
Alex
pawelw1
306 Posts
0
June 29th, 2016 23:00
Hi Alex,
Try to check your gatewayUser.properties file to see if it's poiting to the correct MDM IP addresses. Also see what's in the operations.log and scaleio.log, maybe there is some clue?
Best,
Pawel
pawelw1
306 Posts
0
June 25th, 2016 02:00
Hi Alex,
Not sure about ReXRey, but you are certain about the way you authenticate against the Gateway?
First you need to authenticate using /api/login, then use the key you get in response for further requests:
NOT WORKING:
[root@h ~]# curl -k -basic --user admin:XXXXXXXXXX https://1.2.3.4/api
{ "message" : "Unauthorized", "httpStatusCode" : 401, "errorCode" : 0
WORKING:
[root@h ~]# curl -k --basic --user admin:XXXXXXXXXX https://1.2.3.4/api/login "YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
[root@h ~]# curl -k --basic --user admin:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY https://1.2.3.4/api/types/System/instances
[{"mdmManagementIpList":["1.2.3.4","2.3.4.5"] (...)
Let me know if you can get it working using curl - if yes, check the gateway properties to make sure you point to the correct MDM IP addresses etc.
Thanks,
Pawel
AlexKamalovBNY
5 Posts
0
June 27th, 2016 05:00
Thank you Pawel.Glab Just wanted to mention that I am running ScaleIO 2.x. As far as command goes, unfortunately it did not work. See below:
[root@node5 etc]# curl -k --basic --user admin:XXXXX https://192.168.120.166/api/login
{"message":"Unauthorized","httpStatusCode":401,"errorCode":0}[root@node5 etc]#
Alex
pawelw1
306 Posts
0
June 30th, 2016 12:00
Happy I could help Alex :-)
AlexKamalovBNY
5 Posts
0
June 30th, 2016 12:00
You're absolutely correct Pawel Orzechowski. The problem was due to unapproved certificate in Gateway. Once approved, the environment normalized. Thanks again!!
Alex
SysEng777
25 Posts
0
August 10th, 2016 14:00
Alex,
I am having the same issue. How did you approve the certificate?
I figured out my problem. I was using the gateway admin username and password instead of the root username and password when registering the gateway.