LDAP Resource Reconciliation

[coocooche]

Hi,
I installed OpenDS and i created a ldap resource to test Velo. Now i
want to reconciliate the LDAP resource with VELO and i want to map
these resource's attributes with the VELO's ones (as I did with jdbc
resource). I've noticed that Velo support only Active Directory and
that the adapter (velo.adapters.ActiveDirectoryAdapter) gives me
“successfully” when I try the test connectivity (so it connect to my
OpenDS). Well, after that i'm going to write my groovy script to
reconciliate. I tried to write my script to do a search on ldap and
I've noticed that I need the lib: 'groovy-ldap.jar'. Can you tell me
please where can I put this lib (which directory on velo?) so than I
can import at my groovy script?

Thanks

[baba]

Hi,
My assumption is that you have two options :

1.after build : {JBOSS basedir}/server/default/deploy/velo.ear/lib
2.in source : under sub-folder "lib"

Notify if this works for you .

[coocooche]

Hey,
i have a ldap resource with the attributes:username,name,surname and
email. I created the groovy script for the LDAP Reconcilation as
follow:

import org.apache.directory.groovyldap.LDAP
ldap = LDAP.newInstance('ldap://localhost:1389', 'cn=Directory
Manager','password')

def accountsQueryManager = cntx.get("queryManager")
String accountsQuery = ldap.eachEntry(filter:'(uid=*)') {
def username = entry.uid
def name = entry.givenName
def surname = entry.sn
def email = entry.email
}
accountsQueryManager.add(accountsQuery)
cntx.set("queryManager",accountsQueryManager)

This gives me first PENDING task and then RUNNING task but didn't
reconciliate.
Anyone had already done a reconciliation with a ldap resource that
isn't Active Directory?
Is this possibile with Velo 1.4?

Thanks

[Trouby]

Hey,

AD REMOTE ADAPTER is for AD only,
We have LDAP3 resource type, so why using AD if it's an LDAP3 server?

Asaf.

[coocooche]

Hi Asaf, thanks for answering me.
When i created my resource ldapv3 i choosed "Generic LDAP" and i
noticed (in the Additional tab) that the
Adapter Class Name is: "velo.adapters.ActiveDirectoryAdapter". So i
supposed is the same as for Active Directory, isn't it?
If the Adapter class name for ldapv3 is different, please can i have
it?

Anyway, can you tell me please in a few words how can i reconciliate a
ldapv3 resource (OpenDS) on Velo 1.4?
I didn't find anything on wiki and i'm trying to find out how to do
the reconciliation and the provisioning on a ldapv3 resource.

Thanks

[Trouby]

Hey there,
Weird, I just tested, it is
'velo.resource.operationControllers.GenericLdapResourceController' but
there might be a bug somewhere that was fixed during 1.4->1.5
so you can modify it,

It's pretty simple, just map your attributes, the controller will take
care of the creation, automatically.

[coocooche]

I modified and i tried a 'test connectivity' having a failed
operation.
I have the follow exception:
Exception during request processing:
Caused by javax.el.ELException with message:
"javax.ejb.EJBTransactionRolledbackException:
velo.resource.operationControllers.GenericLdapResourceController
cannot be cast to velo.adapters.ResourceAdapter"

[Trouby]

You have changed in the wrong place,
I'm sorry if I confused you, leave the value of the adapter as it was,

On the RESOURCE_TYPE (top menu resources>resource types), make sure
that the LDAP3 resource type controller is
'velo.resource.operationControllers.GenericLdapResourceController'
Not in the adapter when editing the resource,

thanks.

[coocooche]

Hi,
I set the ldap3 resource type controller in
'velo.resource.operationControllers.GenericLdapResourceController' and
the adapter in the resourse is set in
'velo.adapters.ActiveDirectoryAdapter'. The 'Test Connectivity' is ok
but executing the task, I receive a FATAL_ERROR:'Failed to perform the
operation, failure message: Not supported yet' !!!!
Sorry for boring you but I can't get out the reconciliation without
your help. May you please post an entire example of a ldap3
reconciliation (adapter name,groovy script if exist for the
reconciliation etc)?? I'm always using Velo 1.4.

Thanks.