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

Release user can't load model via the cli #120

Closed
elutfall opened this Issue Feb 1, 2012 · 4 comments

Comments

Projects
None yet
2 participants
@elutfall

elutfall commented Feb 1, 2012

Using 4.1.1, a release user can load the model via the UI as well as get status via the cli.

When te release user tries to load the model via the cli, they get an access error:

Enter testrelease's password:
Traceback (most recent call last):
File "../glu-tools/console_cli/bin/console-cli.py", line 248, in
main()
File "../glu-tools/console_cli/bin/console-cli.py", line 219, in main
modelLoaded = client.loadModel(modelUrl = options.model, modelFile = options.modelFile)
File "/home/elutfallah/orbitz-fabrics/glu-tools/console_cli/lib/python/gluconsole/rest.py", line 243, in loadModel
response = self._doRequest("model/static", "POST", body)
File "/home/elutfallah/orbitz-fabrics/glu-tools/console_cli/lib/python/gluconsole/rest.py", line 79, in _doRequest
raise restkit.errors.Unauthorized("Unauthorized Request")
restkit.errors.Unauthorized: Unauthorized Request

@ypujante

This comment has been minimized.

Member

ypujante commented Feb 1, 2012

Is this a specific issue with 4.1.1? Or was it also an issue with 4.1.0?

@elutfall

This comment has been minimized.

elutfall commented Feb 6, 2012

Sorry, I was swamped the last couple days. We went from 4.1.0 to 4.1.1 so quickly, I didn't test this in 4.1.0.

What it seems like is that the access control for the release user is different via the UI than the REST api.

@ypujante

This comment has been minimized.

Member

ypujante commented Feb 15, 2012

After checking the code, for REST calls that are neither GET nor HEAD (in other words all write calls), only ADMIN has been authorized. This has been the case since day 1 and is not an issue that was introduced recently. That being said with 4.2.0 I will make it configurable if you want to 'downgrade' to RELEASE instead of ADMIN.

@ypujante

This comment has been minimized.

Member

ypujante commented Feb 16, 2012

It is now configurable in 4.2.0

@ypujante ypujante closed this Feb 16, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment