Achieve dynamic authentication in a Web services client using a custom JAAS callback handler
From the developerWorks archives
Date archived: January 3, 2017 | First published: July 18, 2007
It is often the case that a statically defined username and password in the Web services deployment descriptor is not appropriate. With the Java™ Authentication and Authorization Service (JAAS) callback handler described in this article, you have the option of using a properties file (or some other source) for dynamically setting username and password at run time for UsernameToken (UNT) authentication in a Web services client. This article describes a sample application that uses such a custom callback handler, enabling you to send a different username and password for each client application user. This content is part of the IBM WebSphere Developer Technical Journal.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.