Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4049578
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T13:57:45+00:00 2026-05-20T13:57:45+00:00

If a user has a permissions user:edit:1 and I’m using the annotation driven @RequiresPermissions(user:edit)

  • 0

If a user has a permissions user:edit:1 and I’m using the annotation driven @RequiresPermissions("user:edit") why is shiro throwing an exception? Shouldn’t that permission be implied by the fact that they have user:edit:1? If I put @RequriesPermissions("user:edit:1") then it works fine but during the context of operation I won’t know what 1 is yet so that will be checked later in the method, but I’d like to avoid going into the method at all if they don’t have the user:edit permission at all.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T13:57:46+00:00Added an answer on May 20, 2026 at 1:57 pm

    "user:edit" implies "user:edit:1" but not the other way around.
    You can keep using @RequiresPermissions("user:edit") and then check for the “1” in your method. You can also use a wildcard @RequiresPermissions("user:edit:*"), which is the exactly the same but I think it’s clearer.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is there a way to set up a user group that has permissions to
If I have a user that only has limited permissions - just db_datareader and
I've got two objects: User and Permission, where User has a Collection. In my
I've got the following situation: A User object has a Set of Permission objects
A user has sent me some information that they posted to one of my
I have a site where a user can have multiple permissions (view, edit, delete,
My app has authentication and for the user to be able to edit some
I need to make sure a user has the correct permissions before allowing them
I have a document library with a workflow that dynamicly sets user permissions to
After reading this tidbit , it would seem that the current user's permission would

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.