IceWarp Connector

This connector can be used to connect to email client IceWarp. Communication is via API which is provided by the end system.

Connector has few settings which need to be configured before you used it.

Adress where email client is running.

Username for account which will be used for communication with the end system.

Password for account.

Domain on IceWarp server where users are stored. If you want to connect more than one domain in same IceWarp server you should create new system connection for every domain.

There are two types of object which are supported in current version of connector. __ACCOUNT__ for users and __GROUP__ for roles If you want connect both types make two systems in IdM, with different configuration.

You can activate debug mode by this property to see xml requests in log. This will only work if logging is configured in logback-spring.xml. Find your active profile in this file and check for this configuration:

<logger name="eu.bcvsolutions" level="INFO"/>

(when using "production" profile, idm choose "default" profile because there is no production configuration)

2019-01-08 10:52:12.509  INFO 2729 --- [nio-8080-exec-2] e.b.idm.connector.IceWarpConnector       : ICEWARP REQUEST XML BODY
2019-01-08 10:52:12.510  INFO 2729 --- [nio-8080-exec-2] e.b.idm.connector.IceWarpConnector       : <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<iq sid="">
    <query xmlns="admin:iq:rpc">
        <commandname>logout</commandname>
        <commandparams xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="logout"/>
    </query>
</iq>

Schema generation is supported by connector. It will generate these schemas:

__ACCOUNT__

__GROUP__

• firstname
• lastname
• email – email address
• displayemail – same as email
• accounttype - managed values: 0 = User, 7 = Group (possible values: 0 - User, 1 - Mailing list, 2 - Executable, 3 - Notification, 4 - Static Route, 5 - Catalog, 6 - List server, 7 - Group)
• accountstate – 0 = enabled, 1 = disabled (login), 2 = disabled (login, receive), 3 = spam trap
• admintype – user / admin: 0 = normal user, 1 = admin. It's important to add EAV selectbox "adminType" for using this attribute.