-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported Scaleio 1.3 Logins ... EMC ScaleIO Version: R1_30.426.0 #19
Comments
If I remember correct, login method and the use of a session key for authentication was a new feature to ease API integration starting with 1.31. Haven't looked into what it takes to get it working with 1.30. Guess the get and post methods could be get its own version specific for 1.30. That obviously need a way to identify version of API when accessing it which do not exist to my knowledge. It's possible to get SIO version after login but not before. |
Yeah, I think all 1.30 needs is the basic auth, no token or login. Here's one way I was thinking. We could add a The tougher part is deciding what to do with the flow of initialization. E.g. ScaleIO calls Just some thoughts, still looking into the best way to do this. I will be looking to help out with this soon to gain 1.30 support for the driver that utilizes scaleiopy. |
Or possibly, idk if you need to login for version, as long as username/password is correct, we could use the version to verify if its 1.30 vs 1.31? This is against a 1.30 (without login)
This is against a 1.31 (without login)
|
Nice find. It's also |
So you use this already? So its possible to set ScaleIO to use a specific version of the API? Also, 2 things, do you think its possible to cut a release before adding any 1.30 or 1.32 support ? E.g. with current feature sets. I will want to refer to this version soon. And when you do the work for 1.32 could we make a separate branch for now? I could do the same for 1.30 work? |
I won´t add any 1.32 stuff before a new release which should be soon. Have some time constraints atm. Need to merge the pieces in v-tree branch and add a minor adjustment to IM class to support configuring syslog during installation and then I´ll create a release out of it. Optimally I´d like to be able to identify protocol version and adopt to it. how come you need 1.30 support? 1.31 do everything that 1.30 do but better. |
Sounds Good, Do you estimate when you'd be able to? Ultimately pip installable releases would be nice too, I know as you mentioned its future roadmap. Agreed, but just for compatibility reasons |
have you succesfully used thi with 1.30? I i'm not sure there is a
/api/login
with 1.30, i am getting errors like below.I can however just use basic auth against the URL
but not /login or api/login
Maybe we can bake in support?
The text was updated successfully, but these errors were encountered: