Custom Authentication Plug-ins
Write your own Java class, implementing one of these two interfaces:
- CustomSSOAuthenticator
- CustomUserPwdAuthenticator
Write an authenticationDescriptor.properties file. The file needs to have at least the following lines (sample data shown in italics):
- tc.displayName=My Authenticator
- tc.uniqueId=MYAUTH
- tc.isSSO=true
- tc.authenticatorClassName=com.mitratech.teamconnect.authentication.provider.TestMySSOAut henticator
It's a good idea to override some default error-message HTML files, too:
- page.badCredentials=loginFailed.html
- page.logout=logout.html
- page.sessionExpired=timeout.html
Put your new class in Document folder System/Authentication/MYAUTH/classes (the folder path must incorporate the value of tc.uniqueId). Put the properties file in there too.
As a sibling of folder classes, create folder pages. Put in HTML files to be used for overriding the default error-condition pages. This is especially important if you're writing an SSO authenticator.
Customizing Message Screens
If you enable an authentication plug-in mechanism in TeamConnect, you can customize the screens that you encounter while accessing and logging out of TeamConnect. You must write, test, and deploy your own Java class to display the customized screens. You should do this step only if you plan to provide extra information for users during their sessions.
Your custom Java class must implement interface javax.servlet.Filter. It should be deployed in the same Documents folder as the configuration files.