Groups > Novell > Designer for Novell Identiry Manager > Re: BUG! Designer using different case than directory




BUG! Designer using different case than directory

BUG! Designer using different case than directory
Fri, 25 Apr 2008 12:13:50 GMT
Designer 3.0 M3 released
IDM 3.6 Roles Based Provisioning Module

Trying to configure Roles Based Provisioning Module and got 2 Files:
SodConflictApproval.prd
SoDConflictApproval.prd

eDirectory has one object
DN:             cn=Sod Conflict Approval, ou=...
Description:    SoD Conflict Approval

Seems that case sensitivy is messing up there. 
Please rely from case sensitivy! That is causing nothing than errors!

See also bug reported in the Workflow-Forum, where the workflows get new
keys and versions in the database in case of different writing. There is
the problem, that do-start-workflow creates keys with "CN=,OU=,O=" but
the
userApp is creating keys with "cn=,ou=,o=" for the same workflow.


Not funny anymore :-((
Rudi

-- 
As many others, I do not want to get my mailbox full of spam. 
Post Reply
Re: BUG! Designer using different case than directory
Fri, 25 Apr 2008 12:40:52 GMT
On Fri, 25 Apr 2008 12:13:50 +0000, Rudi Synoradzki wrote:

> Designer 3.0 M3 released
> IDM 3.6 Roles Based Provisioning Module
> 
> Trying to configure Roles Based Provisioning Module and got 2 Files:
> SodConflictApproval.prd
> SoDConflictApproval.prd
> 
> eDirectory has one object
> DN:             cn=Sod Conflict Approval, ou=...
> Description:    SoD Conflict Approval
> 
> Seems that case sensitivy is messing up there. 
> Please rely from case sensitivy! That is causing nothing than errors!
> 
> See also bug reported in the Workflow-Forum, where the workflows get new
> keys and versions in the database in case of different writing. There is
> the problem, that do-start-workflow creates keys with
"CN=,OU=,O=" but the
> userApp is creating keys with "cn=,ou=,o=" for the same
workflow.
> 
> 
> Not funny anymore :-((
> Rudi

Hi Rudi,

You should definitely not have two SoD Conflict Approval PRDs.

I've only seen this once on an upgrade from 3.5.1 where the migration
steps weren't followed 100%.

Could you please provide more information on how you got to this stage?
Did you upgrade from a previous version? Did you do a clean install? Did
you create the driver using iManager or Designer?

Any information you can provide will be very helpful in fixing this issue.

Thanks!
Karin Lundberg
Senior Software Engineer
Post Reply
about | contact