Best Practices to use Custom Authentication in shared web server settings

Document created by Pavan_Sirasanambedu Employee on Mar 19, 2015Last modified by jon_brams809399 on Jan 26, 2017
Version 3Show Document
  • View in full screen mode
Guidelines to use custom authentication feature in shared web server settings using Jetty HTTP Authentication Scheme.
Please go through below help links,
http://help.boomi.com/atomsphere/GUID-0D557C0B-B403-4238-98B9-08AFB9B92332.html
http://help.boomi.com/atomsphere/GUID-ED745D36-BD48-444B-9615-39052E3E2F89.html
http://help.boomi.com/atomsphere/GUID-186770BF-0A55-4151-ABA0-C3AC19DA5121

 

Jetty help links for each Module,
http://wiki.eclipse.org/Jetty/Tutorial/JAAS#LdapLoginModule
http://wiki.eclipse.org/Jetty/Tutorial/JAAS#PropertyFileLoginModule
http://wiki.eclipse.org/Jetty/Tutorial/JAAS#JDBCLoginModule

 

Here is help link to download  the required jar file i.e jetty-plus–6.1.26.jar,
http://www.java2s.com/Code/Jar/j/Downloadjettyplus6126jar.htm

 

From the above Jetty help links, configure all necessary settings.

 

Please find attached sample properties file for PropertyFileLoginModule.

 

Note:
1) If you use the PropertyFileLoginModule for authentication, caching is not supported. Therefore if you change authentication information you must restart the Atom or Molecule in order to reset the cache. If you use the LDAPLoginModule or JDBCLoginModule and you change authentication information, you do not need to restart the Atom or Molecule.

 

2) The CUSTOM authentication type is available only for Atoms and Molecules. It can be used only by accounts for which the API Management feature is enabled.

Attachments

Outcomes