Skip to content
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

Saving a new class fails with error "User 'writer' has no the permission to execute the operation 'Update' against the resource:" #153

Closed
krichter722 opened this issue Mar 27, 2015 · 9 comments
Labels
Milestone

Comments

@krichter722
Copy link
Contributor

Saving a new class fails with User 'writer' has no the permission to execute the operation 'Update' against the resource: ResourceGeneric [name=CLUSTER, legacyName=database.cluster].internal. See screenshots for details.

orienteer_demo_not_writable-0

Overview of user writer:

orienteer_demo_not_writable-1

experienced with 1.0-SNAPSHOT

@PhantomYdn
Copy link
Member

Did you try repeat? I had sometimes this bug... It's pretty unpredictable and it seems to be in OrientDB.
And did you try with other class name?

@PhantomYdn PhantomYdn added the bug label Mar 27, 2015
@PhantomYdn PhantomYdn added this to the v1.0 milestone Mar 27, 2015
@krichter722
Copy link
Contributor Author

Reproducible all the time with arbitrary class names and differing and equal short names on all clusters.

@PhantomYdn
Copy link
Member

Related issue in OrientDB: orientechnologies/orientdb#3826

@PhantomYdn
Copy link
Member

Fixed just on demo site, but should be fixed in OrientDB finally.

@krichter722
Copy link
Contributor Author

Can confirm that. Great! Thank you!

@krichter722
Copy link
Contributor Author

I'm now getting this error during saving a new class when I run Orienteer locally on GlassFish 4.1 with cdb7f40. No log entries on the server side.

@krichter722 krichter722 reopened this Apr 8, 2015
@krichter722 krichter722 changed the title Demo no longer writable Saving a new class fails with error "User 'writer' has no the permission to execute the operation 'Update' against the resource:" Apr 8, 2015
@PhantomYdn
Copy link
Member

That's not Orienteer issue, but OrientDB, so it will be repeated everytime when you are using new OrientDB database.

To fix this issue:

  1. Goto 'writer' role (Roles->writer)
  2. Update "Rules" field: put 7 for 'database.cluster.internal'

If you don't mind: please comment here orientechnologies/orientdb#3826 to upvote the issue.

@krichter722
Copy link
Contributor Author

Ahh, thank you. Should work by default, though, right?

@PhantomYdn
Copy link
Member

Yep - that's how it was fixed on demo site.

@PhantomYdn PhantomYdn modified the milestones: v1.1, v1.0 Apr 13, 2015
@PhantomYdn PhantomYdn modified the milestones: v1.1, v1.2 May 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants