Long token name seems to confuse ods-enforcer

Teststeps:
- Initialize token with the name 'SoftHSM123SoftHSM123SoftHSM123So' This token has 32 characters.
- Perform a new setup in ODS (ods-ksmutil setup)
- Sign the zone

Expected result:
- Initialisation of token is successful.
- Signing is successful.

Observed result:
- Initialition of token is successful (see test engine snapshot below --> OTE).
- Signing is unsuccessful (see also syslog below)

Logging OTE: 2011-04-12 16:38:43.512 00438 InitRepo()
2011-04-12 16:38:43.512 Requirement: ODSCC10
2011-04-12 16:38:43.512 RunCommand(softhsm --init-token --slot 1 --label SoftHSM123SoftHSM123SoftHSM123So --so-pin 4321 --pin 4321)
Assuming softhsm --init-token --slot 1 --label SoftHSM123SoftHSM123SoftHSM123So --so-pin 4321 --pin 4321 is a process!
2011-04-12 16:38:44.336
- runCommand: Process started, PID: 6861
2011-04-12 16:38:44.336 OUTPUT: The token has been initialized.

Logging Syslog:
Apr 12 16:39:15 DEVELOPER15 ods-enforcerd: hsm_get_slot_id(): could not find token with the name #012SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM123SoftHSM
Apr 12 16:39:20 DEVELOPER15 ods-signerd: setup failed: error initializing libhsm (errno 268435457)