-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Unhelpful error message when trying to create as a denied submitter #1573
Comments
Hem. Are you sure you used a valid token? Metacat checks if the token is valid before if a user is in the white list. I checked the code and the error message says the user is not allowed to insert or update objects in the node. I can change it to say it is not in the allowed submitter list. |
Can't reproduce -- see steps below. Agree with @taojing2002 comment above -- guessing the report is erroneous. Will add text to the error message, indicating reason for insert/update restriction. STR:
Observed (MB):
|
@artntek Thank you, Matthew. I think Lauren used an invalid token to get a different error message. However, the message still is not very clear - the user is not allowed to insert/update for this specific object or anything, which is our case.
If we can explicitly say the user is not in the allowed-user-list on this node, it can be much more helpful. |
@artntek Sorry, I skipped one line on your comment - you already have the plan to update the error text :) |
bugfix for #1573 -- Error Message Enhancement
I am attempting to submit an object to a Metacat that is configured with a "allowed submitter" list. My identity is not in the allowed submitter list, so I expect an error message when I try to submit an object.
But the error message from Metacat is not very helpful. It is the same message I get when I submit without an auth token:
I think it will be helpful, particularly to repository managers, to get a message that the person is not in the allowed submitter list so that the problem can be solved for that user.
The text was updated successfully, but these errors were encountered: