Hi Thea,

Yes you can do it by using the LDAP component from forge. You can create a timer and run the code to fetch data from Active Directory and push it in Outsystems.( for ex,. Method Group_Getmembers)

You need to pass the path carefully as it will return the result by that filter only

Example of Path .

"CN=ABC,OU=fgh,OU=pqs,OU=mycompdomain,DC=abc,DC=mycompdomain,DC=com" 

Regards

-PJ-

Hi Thea,

Because there are some Outsystems licensing models that depend of the number of active users, the Users eSpace does not create/import users automatically, only when the user logs in.

Regarding documentation:

On LDAP forge component you have one eSpace demo, but basically you will be querying the LDAP server, so the documentation that you will need is related with LDAP, as example https://technet.microsoft.com/en-us/library/aa996205(v=exchg.65).aspx

Here you can find the Outsystems documentation about the configuration of the users eSpace:

https://success.outsystems.com/Documentation/10/Developing_an_Application/Secure_the_Application/End-User_Management/End-User_Authentication/Configuring_End-User_Authentication

Please note that you can also find in Authentication extension (part of the System components), some LDAP actions, so you might not need to use the forge component:

Hope it helps you.

Hi Thea,

There is no useful document available which can tell you how to use this component.

Regards

-PJ-

Hi Thea,

Please understand that majority of Forge component was from Community Member, and as such it's at creator discretion whether he/she will made documentation.

I wouldn't said it was deal breaker.

This one thing should not over-shadowing the whole greatness of Outsystems Platform.

Time spent exploring and making logic to synchronize AD Users and Groups to Outsystems Users and Groups is very minuscule compared to what you will save for development of web/mobile apps.

BTW, are you using on-premise Outsystems Platform server?

You said your AD server was on-premise.

Your AD server should be reachable from the internet if you're using Outsystems Cloud Server.

Hi Thea,

Without knowing your LDAP structure is almost impossible to help.

What are you trying to achieve with the LDAP module, what error is being thrown?

Basically you will need to know your AD structure, as example: 

https://www.websense.com/content/support/library/web/hosted/dsc_admin/example_schema.aspx

I advise you to use the AD explorer tool, to query and understand your AD structure:

https://docs.microsoft.com/en-us/sysinternals/downloads/adexplorer

If you are able to browse and query your AD with the AD explorer tool, you will be able to use sucessfully the outsystems forge LDAP module component.

Hope it helps you!