ADAM userProxy roadblock

[Joe Kaplan]

For the LDP binary shortcut, I said

\SID:

not

/SID:

Try that instead.

However, if things are behaving consistently, that should give you the same
error that LDIF gave you. Are you sure the SID for the user you are trying
to proxy belongs to a user who is in a domain with a trust relationship to
the domain the ADAM server is joined to?

[Dmitri Gavrilov [MSFT]]

8471 == ERROR_DS_NAME_ERROR_NOT_UNIQUE "Name translation: Input name mapped
to more than one output name."

You are getting a duplicate SID error. You already have either a bindProxy
or a foreignSecurityPrincipal for the SID in this ADAM partition. Remove it,
and you will be able to add the proxy.

[choukse]

Hi All,

I am able to add a user proxy now, but the solution which fixed my problem sounds funny. I just gave a try and created a new ADAM instance and imported the ldf file and it worked this time. The only difference in my previous and current ADAM instance is that, I didn't synchronize the AD and ADAM schema in my new instance. I am not sure that it was the root cause for my problem, but now its working.

Thanks to all of you for the help.

[choukse]

Success....

Hi Joe,

Yes you are right after changing the format to \SID, I still got the same error as of LDIF. I was passing the right SID.

I just did a hit and trial by creating a new instance and it worked. The only difference in my previous and current ADAM instance is that, I didn't synchronize the AD and ADAM schema in my new instance.

Hi Dmitri,

Yes your solution worked for me. I had same SID in foreignSecurityPrincipal in my previous ADAM instance. After removing the SID from foreignSecurityPrincipal, I am able to successfully add the userProxy in my previous ADAM instance as well. I think thats why I was able to add userProxy in my new instance, since it doesn't have the foreignSecurityPrincipal at all.

Thanks to all of you for the help.

[sawyej3]

Hi all,

I recently had to go through the same trials by starting up a new ADAM instance because of ForeignSecurityPrincipal (I think). It's now on port 50000 because 389 was for 'instance 1'. No big deal, but now I cannot bind to that old instance. I thought this was application mode (i.e. possibility of more than one instance?) No big deal either, really...

My biggest concern is now that I have access through userproxy, why can I not connect to the ADAM instance in ADSI edit, only through Ldp.exe???

Thanks,
John

[Lee Flight]

Hi

the userProxy objects were designed for backward compatability
with applications that perform LDAP simple bind and so LDAP
simple bind was made requirement for userProxy authentication.
ADSIEdit prior to WS08 does not have the ability to perform
a LDAP simple bind so it's a limitation of earlier versions the tool.

Lee Flight

"sawyej3" <sawyej3.3lwrrb@DoNotSpam.com> wrote in message
news:sawyej3.3lwrrb@DoNotSpam.com...
>
> Hi all,
>
> I recently had to go through the same trials by starting up a new ADAM
> instance because of ForeignSecurityPrincipal (I think). It's now on port
> 50000 because 389 was for 'instance 1'. No big deal, but now I cannot
> bind to that old instance. I thought this was application mode (i.e.
> possibility of more than one instance?) No big deal either, really...
>
> My biggest concern is now that I have access through userproxy, why can
> I not connect to the ADAM instance in ADSI edit, only through
> Ldp.exe???
>
> Thanks,
> John
>
>
> --
> sawyej3
> ------------------------------------------------------------------------
> sawyej3's Profile: http://forums.techarena.in/members/sawyej3.htm
> View this thread: ADAM userProxy roadblock
>
> http://forums.techarena.in
>

[sawyej3]

Lee,

Ugh, guess I should have thought of that... Fairly obvious, and now it definatley makes sense.

Thank you!

John

Hi

the userProxy objects were designed for backward compatability
with applications that perform LDAP simple bind and so LDAP
simple bind was made requirement for userProxy authentication.
ADSIEdit prior to WS08 does not have the ability to perform
a LDAP simple bind so it's a limitation of earlier versions the tool.

Lee Flight

"sawyej3" <sawyej3.3lwrrb@DoNotSpam.com> wrote in message
news:sawyej3.3lwrrb@DoNotSpam.com...
>
> Hi all,
>
> I recently had to go through the same trials by starting up a new ADAM
> instance because of ForeignSecurityPrincipal (I think). It's now on port
> 50000 because 389 was for 'instance 1'. No big deal, but now I cannot
> bind to that old instance. I thought this was application mode (i.e.
> possibility of more than one instance?) No big deal either, really...
>
> My biggest concern is now that I have access through userproxy, why can
> I not connect to the ADAM instance in ADSI edit, only through
> Ldp.exe???
>
> Thanks,
> John
>
>
> --
> sawyej3
> ------------------------------------------------------------------------
> sawyej3's Profile: http://forums.techarena.in/members/sawyej3.htm
> View this thread: ADAM userProxy roadblock
>
> http://forums.techarena.in
>