I've created ISIS-799 [1] for this.
[1] https://issues.apache.org/jira/browse/ISIS-799 On 9 June 2014 08:03, Dan Haywood <[email protected]> wrote: > From your description, obviously there's some caching of roles going on > that needs to be cleared. I'm just not sure if it's at the Shiro level, or > in Isis itself. > > Would it be possible for you to share your Shiro configuration so I can > look to reproduce? It'd also be useful for us to add to the website. I > guess I need the shiro.ini, the SQL scripts for creating the tables and > data, and any other referenced configuration files (if any). > > Dan > > > > On 6 June 2014 13:38, <[email protected]> wrote: > >> Hi, >> >> I created security ISIS service (application-specific) to create users, >> roles and permissions and their mappings from UI. >> >> I am facing one issue in the following scenario: >> >> >> 1. Using SQL script one user(admin) with role access to all >> services inserted into security tables >> >> 2. Logged in using admin to create another user(BBY) to access some >> services >> >> 3. Logged out admin >> >> 4. Logged in using BBY. BBY doesn't see those services which are >> given access by admin >> >> 5. Jetty server restart and logged in using BBY >> >> 6. BBY now can be able to see those services. >> >> >> I think when BBY user logs in should see the services as this user has >> got permissions even without restart the server. >> >> The information contained in this electronic message and any attachments >> to this message are intended for the exclusive use of the addressee(s) and >> may contain proprietary, confidential or privileged information. If you are >> not the intended recipient, you should not disseminate, distribute or copy >> this e-mail. Please notify the sender immediately and destroy all copies of >> this message and any attachments. >> >> WARNING: Computer viruses can be transmitted via email. The recipient >> should check this email and any attachments for the presence of viruses. >> The company accepts no liability for any damage caused by any virus >> transmitted by this email. >> >> www.wipro.com >> > >
