Page History

...

I get the error "WorkflowException: ... No outgoing sequence flow..." when updating an user

This When the Activiti workflow adapter is enabled, this means that the given user has a workflow state for which no update is allowed.
Such constraints are contained in the default worklfow XML definition that can be extended an customized through the administration If you want instead to allow such transitions, you will need to update the workflow definition accordingl, through the admin console.

I get the error "An error occurred while registering a ClassTransformer with PersistenceUnitInfo..." during startup

...

      <plugin>
        <groupId>org.codehaus.cargo</groupId>
        <artifactId>cargo-maven2-plugin</artifactId>
        <inherited>true</inherited>
        <configuration>
          <container>
            <timeout>180000</timeout>

...

Sync / Pull Task Execution report not generated when large number of users (e.g. 1000+) exist in MySQL

We can track the cause if we see errors in the core.log as follows:

...

mysql> describe TaskExec;
+-----------+--------------+------+-----+---------+-------+
| Field     | Type         | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| id        | bigint(20)   | NO   | PRI | NULL    |       |
| endDate   | datetime     | YES  |     | NULL    |       |
| message   | mediumtext   | YES  |     | NULL    |       |
| startDate | datetime     | YES  |     | NULL    |       |
| status    | varchar(255) | NO   |     | NULL    |       |
| TASK_ID   | bigint(20)   | YES  | MUL | NULL    |       |
+-----------+--------------+------+-----+---------+-------+
6 rows in set (0.00 sec)

After

...

sync / pull, users do not get assigned any external resource

By default, users are created in Syncope upon synchronization after sync / pull only with data provided by the synchronizing external resource.

If you want to enrich such users, upon create or update after synchronizationsync / pull, you need to provide an UserTemplate for the related Synchronization Task.

Note that this mechanism allows to add various details to synchronizing / pulled users: password, attributes, resources, roles, etc.

...

Include the following information :(<= 1.2.x)

[REST]:[AuthenticationController]:[]:[login]:[SUCCESS]
[REST]:[AuthenticationController]:[]:[login]:[FAILURE]

...