Overview of security roles

Here are the security roles known by the Frank!Framework:

IbisWebService

Can call an Ibis WebserviceListener. No access to Ladybug.

IbisObserver

Can look in configurations, statistics and log files. Can view reports, configuration settings, errors and warnings in Ladybug. Can change Ladybug’s default XSLT transformation and node link strategies.

IbisDataAdmin

Can browse message logs, message stores and error stores, see section Processed Messages. Can resend or delete the messages in them. Can reload configurations and start and stop adapters. Can configure when or when not to create Ladybug reports from received messages. Can store and delete Ladybug reports. Has all IbisObserver permissions too.

IbisAdmin

Can do a full reload and has all IbisDataAdmin permissions.

IbisTester

Can execute jdbc query, send jms message, test a service and test a pipeline. Can rerun Ladybug reports. Has all IbisAdmin and IbisWebService permissions too.

Note

“What is ‘Ibis’?”, you might ask. This comes from the time before the frankemwork was renamed to Frank!Framework. In that time, the brands “Ibis” and “Ibis Adapter Framework” were used. These names have not all been replaced by their Frank! equivalents.