Moving secured documents between Oracle IRM Hot Folders
By Simon Thorpe on Nov 25, 2009
A customer recently asked how do they handle the following;
A document which is in IRM protected folder A is now moved to IRM protected folder B. In such a case what will happen to the classification tied to the document? Will the earlier classification remain with the document or the document will now inherit the new classification which is B.
The customer is looking at using our Hot Folders functionality which monitors folders for new files and automatically seals them to the correct classification. The problem is, what happens if a user moves a sealed document from one Hot Folder to another?
Oracle IRM Hot Folders can be configured to associate different classifications with the A and B folders and then take one of several alternative actions if it encounters a file sealed to the A context in the B folder:
- It can warn (to the log) and do nothing. This is the default.
- It can quarantine the file to another folder.
- It can reseal the file to the B context.
In the last option the user account under which IRM Hot Folders is operating must have the appropriate rights in the source (A) and destination (B) contexts. Also - IRM Hot Folders (and the underlying IRM web services) only support resealing between contexts defined on the same IRM Server.
So it's the customer's choice as to what to do, no need to write any code, just configure the software.