I'm having some trouble deploying a custom login implementation as part of a WDK application.
Use Case: We had a custom plugin developed for us so that a user can log into Webtop with their employee ID and a token based authentication card. It validates this information against our organizations LDAP.
The 1st problem: This plugin works when logging into the content server utilities like API and DQL . It does also log an employee into the Webtop, but then fails when searching for documents (the search hangs with "undefined undefined").
The partial solution: After working with EMC support, they had us append the string DM_PLUGIN=companyldap/ (where companyldap is the name or our custom plugin) before the token password in the Webtop login screen. This allows to a user to successfully login and successfully search.
Now of course it is very poor form to have all our users remember to and successfully type DM_PLUGIN=companyldap/ into the password field every time they login. So I have been attempting to extend the login form to append that string when the Login button is clicked. I believe I have everything configured correctly for this, but I'm having a problem redeploying the app from Weblogic. I get the following error:
Can't locate a unique child element with path: pages.start in: ([...]/webtop/config/loginex_component.xml)config[version=1.0].scope[application=webtop,version=latest].component[extends=login:wdk/config/loginex_component.xml,id=login,version=latest].
The path is specified by: ([...]/custom/config/login_modifies.xml)config[version=1.0].scope[application=custom].component[modifies=login:webtop/config/loginex_component.xml].replace[path=pages.start]
Here is my login_modifies.xml file:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<config version="1.0">
<scope>
<component modifies="login:webtop/config/loginex_component.xml">
<replace path="pages.start">
<start>/custom/jsp/login/loginex.jsp</start>
</replace>
<replace path="class">
<class>com.mycompany.MyLogin</class>
</replace>
</component>
</scope>
</config>
I would appreciate any help in the right direction. Thanks for you time!
-Sean
