developer-delphi-active-directory

To orchestrate Active Directory integration in Delphi, this skill routes LDAP and AD queries to specialized sub-skills (expert, roteiro, estrutura) based on user intent. It provides a central entry point to guide setup, authentication, and configuration workflows without implementing AD logic directly.

The best way to structure LDAP authentication logic is using a three-skill orchestration model. This approach coordinates specialized sub-skills for setup, queries, and configuration, ensuring your Delphi projects maintain a canonical entry point for all AD integration tasks.

Yes, you can route queries involving TActiveDirectory and ldapsend. The orchestrator specifically targets inquiries referencing these components, alongside IActiveDirectoryService and USE_LDAP, directing them to the appropriate specialized sub-skill for AD integration implementation.

You need an LDAP orchestration model when managing Active Directory integration across multiple Delphi projects. It becomes necessary when your workflows require coordinated routing for setup, authentication, queries, and configuration tasks rather than implementing AD logic directly within each project.

Delphi LDAP integration uses a three-family skill set: expert, roteiro, and estrutura. This separation allows the orchestrator to route queries to the appropriate sub-skill based on specific user intent, covering setup, authentication, queries, and configuration workflows distinctly.

Using an orchestrator avoids implementing Active Directory logic directly by providing a central entry point to manage LDAP integration. It routes queries to correct specialized skills, enforcing a structured three-skill orchestration model that guides AD workflows consistently across Delphi projects.