Please find the attached files

I Ryan,

Are you able to perform any other action, like listing the users or groups?

Hi Renato Pauleta, 

Possible help to fix?

Thank you

Regards,

Ryan

Hi Ryan,

Sorry for the delay.

This may be related to the underlying connection used to perform the login validation. Or it may be the domain, but I don't think it is based on what you said that you're able to perform other actions.

Looking at the screenshot you've provided, I do have a question. Are you using ActiveDirectory_IS directly? But I don't see the GlobalDirectoryEntry_Set action anywhere. Where are you running it? This should be run before to set the connection properly. Alternatively, you can use the https://www.outsystems.com/forge/component-overview/11128/active-directory-core-simplified component that wraps this one and makes it easier to call the AD. It also includes a Demo that shows how to use it.

Hi Renato Pauleta,

I just know need to add GlobalDirectoryEntry_Set and set the Domain name.

Now able to work already.

May I know what is the different between _BL, _CS, _Ext, _IS

Thank you

Regards,

Ryan

Hi Ryan.

First of all, I'm happy to know things are working now!

These are just a part of helping know what we have in each module/extension

• _ext is the extension it's what allows us to extend the .NET code with the OutSystems platform
• _IS is the "integration service" it wraps the code from the extension (_ext) with no logic
• _CS is the "core service" it has the core entities that support the access token CRUD in this case
• _BL is the "business logic" it has some logic and uses the _IS but simplifies the process of making a connection to the AD by making use of tokens that you can manage in the Backoffice

The BL does the GlobalDirectoryEntry_Set in all actions that you call without you having to specify it, so long as you have a token created in the backoffice that has the information about your connection.