Interception point

As for many other things in InfoGlue Management tool this is mostly a part of the system aimed at the administrator but we still want to say a few words about this feature.

Interception points are what replaced “Functions” from 1.2. An interception point is a point in the system where we have added a possibility for custom logic to intercept the processing and extend Infoglue’s own logic.

We use this feature for many things and we think it will be used even more by the customers themselves later on. The most obvious example of how we use the feature is how the entire authorization system uses it to intercept actions made by the user in the system and checks if the user is allowed to do what he/she tries to do. If not - the authorizer puts in a veto and stops the action.

The interfaces in the management tool are very simple. The first one which meets you when you clicked on the InterceptionPoint-link is:

By default when a new system has been installed this list will contain some interception points incorporated in the core but not all will be activated. You can add more of the core ones or course you can add new ones for your own code but you are not able to add more system points unless you compile the system yourself.

The detail view looks like this:

The fields available for editing are:

Field name

Typical values



ManagementTool, Content etc

The category is used when showing different views, especially when grouping the interception points when assigning access rights.


ManagementTool.Read, Content.Read

This is what the code use as a reference when an interception point is reached.


Free text

Just description of the interception point

Uses extra data for access control

No / Yes

If yes the system knows that the access right-dialog must be initiated from a point in the tools which identifies an entity more in detail. If no there will be an “Access Rights”-button in this interface. This means that things like which users has access to the content tool, management tool etc should be configured from the respective Interception point but things like content access which is different for each content must be configured from it’s view.

As you see there is a list(only one item now) below of interceptors. This is a way which makes it possible to attach any number of interceptors to an interception point very much like a listener. If you don’t want any access rights checked for example you can just uncheck the “InfoGlue Common Access Rights Interceptor” for that interception point. Not recommended but possible.

The core interception points have descriptions added to them which we hope is enough to guide you to what they do. Let us know if you need more descriptions/documentation.