Role based access at template level

Hi Ram,

I will try to let you know once I figure it out :-) 

These posts concern work in progress, which means that I have not implemented a complete solution yet, and there are still pieces missing. 

Please note that implementing role based access in itself is no problem, but you can only do it at the entry/item level (i.e. for each file or directory in the repository). What I am working on now is how to restrict access to individual value holders in a template. That means that you might have write access to the file itself, but you may not change everything in the file, for example general policy rules. 

If what you need is role based authorization for files, all you need to do is to implement the com.blazesoft.repository.file.NdRepositoryAuthorizationManager. Your implementation would need to pick up roles based on username/password from some source (file/database/LDAP/AD/etc). You would also need to create a model that describes what any given role has access to. 

Did that make sense? 

Regards, 

Jostein