Hi Daniel, The mid-tier part is explained in the doc wiki at this url: https://docs.bmc.com/docs/display/public/ars201401/Integrating+the+mid+tier+into+an+SSO+environment
To sum it up, it's kinda like this: -> copy your authenticator jar file (and libs if needed) in "/WEB-INF/lib/" from the mid-tier, -> copy your authenticator properties file (let's say "myauthenticator.properties") into "/WEB-INF/classes/" from mid-tier, -> config BMC "/WEB-INF/classes/config.properties" to tell to use your authenticator: --> arsystem.authenticator=YourAuthenticatorPackage.YourAuthenticatorClass --> arsystem.authenticator.config.file=myauthenticator.properties --> I did not have to change "arsystem.authenticator.sso.enckey" when I did mine for Engage 2014, That's pretty much all Mid-Tier side... I did an authenticator plugin and AREA plugin and videos for the BMC Engage 2014 but I don't think I can post it here since it's something dedicated for BMC Engage (same as for wwrug I guess we are not expected to share it to people who did not attend)... Was the question only for Mid-Tier or also ARS side? Best regards. Laurent. Best regards. Laurent. On 17 Mar, 2016, at 11:48 AM, Daniel Wu <danie...@cox.net> wrote: We are trying to create our own custom Java authentication provider. I found a Java authenticator sample, but there is no documentation or guideline on where to put those compiled jar files or the properties files. If someone has any documentation on the custom Java, it would be greatly appreciated. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
