Did anyone try LDAP in webembeds? can you let me know how the sample script will look like with LDAP.

sample script for basic authentication is given below, is there any additional elements to be passed for LDAP

<script src='https://<your-domain>/prweb/PRRestService/c11nsvc/v1/pega-embed.js'></script>

<pega-embed    id='theEmbed'    action='createCase'    caseTypeID='<<your-case-type-id>>'    themeID='<<your-theme-id>>'    casePage='assignment'    assignmentHeader='false'    appAlias='<<your-app-alias>>'    pegaServerUrl='https://<your-domain>/prweb/'    autoReauth='true'    authService='<<your-auth-service>>' 

  grantType='authCode'   clientId='<<your-client-id>>'    style='width:100%'> </pega-embed>

Note: LDAP is configured and works fine

Silent authentication

Web embeds support a number of configurations to obtain authentication without displaying a challenge screen:

grantType="authCode" with WebLDAP

You can use a WebLDAP1, WebLDAP2, or WebLDAP3 custom authentication service with the authorization code grant flow.

In this scenario, you can configure the authentication service Rule to include an Activity that takes in inputs to the request, such as cookies, and maps them to a specific dynamic operator or rejects the request. This Activity must be included in a Ruleset that is explicitly listed in the PEGA!BROWSER:Unauthenticated Access Group of the current requestor type.

In addition, the Source of operator credentials field in the authentication service must be set to Use Credentials Stored in PegaRULES.

Finally, you must ensure that security settings on any of the servers are not blocking the OAuth 2.0 client redirects in a hidden iframe. The redirects need to be configured to succeed in a specified interval, with the default interval set to five seconds. If the redirects fail in the iframe, a pop-up window might appear and disappear because the web embed expects the challenge, but the IDP returns the authentication code immediately, which causes the web embed to close the window.