This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi. I am wondering if it is possible to create an internal access control model in a Java application based on classes that attempt to access certain methods or classes ?
My idea is that a Java application with plugin capabilities may have certain methods or classes too sensitive for plugin classes to access. E.g. secure storage or user password authentication classes shouldn't be accessed by plugins at all.
I was wondering if it is possible to use XXXClass.getClass() which returns a "Class" class object to do checking against an access control list for the system ?
Is it practically safe to do so too ?
I am wondering maybe some malicious classes may try to spoof a Class object to gain access or maybe is it possible for some malicious class to take control of a legitimate class to access restricted areas in an application system ?
If using "Class" class objects to determine the ability to access restricted classes or methods are not safe, is there a set of samples that can be created to proof that this method of access control between classes and methods are not safe ?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com