[ https://issues.apache.org/jira/browse/RAMPART-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546212 ]
Nandana Mihindukulasooriya commented on RAMPART-72: --------------------------------------------------- I think this is fixed in the Rampart trunk. Now we first try to get the username and the password from the options instance in the message context. If that is not found, then we get the username from the Rampart Config and the password from the callback. //Get the user //First try options Options options = rmd.getMsgContext().getOptions(); String user = options.getUserName(); if(user == null || user.length() == 0) { //Then try RampartConfig if(rpd.getRampartConfig() != null) { user = rpd.getRampartConfig().getUser(); } } if(user != null && !"".equals(user)) { log.debug("User : " + user); //Get the password //First check options object for a password String password = options.getPassword(); if((password == null || password.length() == 0) && rpd.getRampartConfig() != null) { //Then try to get the password from the given callback handler CallbackHandler handler = RampartUtil.getPasswordCB(rmd); > Use username and password available in the Options instance in the message > context in adding a UsernameToken > ------------------------------------------------------------------------------------------------------------ > > Key: RAMPART-72 > URL: https://issues.apache.org/jira/browse/RAMPART-72 > Project: Rampart > Issue Type: Improvement > Affects Versions: 1.3 > Reporter: Ruchith Udayanga Fernando > Assignee: Ruchith Udayanga Fernando > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.