[prev in list] [next in list] [prev in thread] [next in thread] 

List:       forgerock-openidm
Subject:    [OpenIDM] AD Connector Server Error - Access is Denied
From:       sasi.kelam () idamta ! com (Sasi Kelam)
Date:       2012-04-16 2:29:16
Message-ID: F78C675A-94D2-4DBD-BA81-BC9B817F0168 () idamta ! com
[Download RAW message or body]

Hi Gael,

You suggestion worked, when we changed the LDAP Host name to 127.0.0.1 we are not \
getting the error anymore, the reason we thing we are getting Access Denied is \
because of the Gateway not able to resolve the External IP Address of the Amazon \
Cloud Server.

- Open IDM (In Lab)   => Active Directory DC + Connector Server (Amazon Cloud)

OpenIDM can resolve the IP Address of the cloud connector server but because we have \
the same name in the connector json & AD provisioner json, the AD provisioner json \
was not able to resolve the external cloud servername so its giving us access denied. \
Now everything works after changing the the LDAP Host Name to 127.0.0.1.

Thanks for the help.

Regards,
Sasi


Begin forwarded message:

> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 13 Apr 2012 18:26:19 +0200
> From: Gael Allioux <gael.allioux at forgerock.com>
> Subject: Re: [OpenIDM] AD Connector Server Error - Access is Denied
> 	(Matthias Tristl)
> To: openidm at forgerock.org
> Message-ID: <4F8853AB.5060706 at forgerock.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> An HTML attachment was scrubbed...
> URL: http://lists.forgerock.org/pipermail/openidm/attachments/20120413/1b1b989a/attachment.html \
>  
> ------------------------------
> 
> _______________________________________________
> OpenIDM mailing list
> OpenIDM at forgerock.org
> https://lists.forgerock.org/mailman/listinfo/openidm
> 
> 
> End of OpenIDM Digest, Vol 23, Issue 17
> ***************************************
> 


[prev in list] [next in list] [prev in thread] [next in thread]