|
| Re: BUG! Designer using different case than directory |
 |
Fri, 25 Apr 2008 15:13:32 GMT |
Karin, hi!
I did a fresh install from the UAProv 3.6 dvd download and then created the
initial UserApp Driver using Designer 3.0 M3 (release Version). I could
deploy it.
As I run in trouble with the Roles Services Driver then I used IManager to
check and verify all settings.
After that I did a compare and updated Designer, but did not really look
what was suggested, so I run the update into Designer.
I compared again, and had differences. So I wanted to deploy again. This
ended in an error, caused by the two prd's.
Thanks
Rudi
Karin Lundberg wrote:
> 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
> Novell, Inc.
--
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 15:47:06 GMT |
On 04/25/2008 10:13 AM, Rudi Synoradzki wrote:
> Karin, hi!
>
> I did a fresh install from the UAProv 3.6 dvd download and then created
the
> initial UserApp Driver using Designer 3.0 M3 (release Version). I could
> deploy it.
>
I would strongly suggest using Designer 2.1.1 with the Roles updates for
2.1.1 instead of 3.0 anything.
|
| Post Reply
|
| Re: BUG! Designer using different case than directory |
 |
Fri, 25 Apr 2008 15:57:56 GMT |
Hi Rudi,
I'm not sure what's going on.
I'll have our testers test this scenario and try to reproduce so we can
make sure this doesn't appear in the final release of Designer 3.0.
Thanks,
Karin
On Fri, 25 Apr 2008 15:13:32 +0000, Rudi Synoradzki wrote:
> Karin, hi!
>
> I did a fresh install from the UAProv 3.6 dvd download and then created
the
> initial UserApp Driver using Designer 3.0 M3 (release Version). I could
> deploy it.
>
> As I run in trouble with the Roles Services Driver then I used IManager to
> check and verify all settings.
>
> After that I did a compare and updated Designer, but did not really look
> what was suggested, so I run the update into Designer.
>
> I compared again, and had differences. So I wanted to deploy again. This
> ended in an error, caused by the two prd's.
>
> Thanks
> Rudi
>
>
> Karin Lundberg wrote:
>
>> 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
>> Novell, Inc.
|
| Post Reply
|
| Re: BUG! Designer using different case than directory |
 |
Sun, 27 Apr 2008 21:07:51 GMT |
Works fine with Designer 2.11 following John's advice...
Rudi
Rudi Synoradzki wrote:
> Karin, hi!
>
> I did a fresh install from the UAProv 3.6 dvd download and then created
> the initial UserApp Driver using Designer 3.0 M3 (release Version). I
> could deploy it.
>
> As I run in trouble with the Roles Services Driver then I used IManager to
> check and verify all settings.
>
> After that I did a compare and updated Designer, but did not really look
> what was suggested, so I run the update into Designer.
>
> I compared again, and had differences. So I wanted to deploy again. This
> ended in an error, caused by the two prd's.
>
> Thanks
> Rudi
>
>
> Karin Lundberg wrote:
>
>> 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
>> Novell, Inc.
>
--
As many others, I do not want to get my mailbox full of spam.
|
| Post Reply
|
|
|