Example usage for javax.security.auth.callback CallbackHandler interface-usage

Introduction

In this page you can find the example usage for javax.security.auth.callback CallbackHandler interface-usage.

Usage

From source file org.josso.jaspi.agent.JASPICallbackHandler.java

/**
 * Callback handler for JASPI Web Profile.
 */
public class JASPICallbackHandler implements CallbackHandler {

    private static final Log log = LogFactory.getLog(JASPICallbackHandler.class);

From source file org.wso2.carbon.identity.sts.mgt.IPPasswordCallbackHandler.java

public class IPPasswordCallbackHandler implements CallbackHandler {

    private static final Log log = LogFactory.getLog(IPPasswordCallbackHandler.class);

    public IPPasswordCallbackHandler() {

From source file org.wso2.carbon.micro.integrator.security.callback.AbstractPasswordCallback.java

/**
 * This class handles the authentication of the username token via the defined user store.
 * This class can be inherited to write a password callback handler, by implementing the getRealmConfig method.
 */
public abstract class AbstractPasswordCallback implements CallbackHandler {

From source file com.alfaariss.oa.profile.aselect.ws.security.PWCBHandler.java

/**
 * Password callback handler for secure webservices.
 *
 * @author EVB
 * @author Alfa & Ariss
 * @since 1.4

From source file org.ojbc.util.camel.security.saml.OJBSamlCallbackHandler.java

/**
 * This callback handler will retrieve a SAML token from the OJBSamlMap
 * using a 'tokenID' as the key.  Token ID is in the CXF headers as Camel
 * copies headers to the CXF message.  See here for more information:
 * 
 * @see http://cxf.547215.n5.nabble.com/WS-Security-Policy-with-Existing-SAML-Token-tc5720608.html

From source file org.apache.ws.security.handler.SignatureUTAliasTest.java

/**
 * This is a test for WSS-194 - "Support overriding KeyStore alias for signature so that it can
 * be different than user name used for UsernameToken".
 */
public class SignatureUTAliasTest extends org.junit.Assert implements CallbackHandler {
    private static final org.apache.commons.logging.Log LOG = org.apache.commons.logging.LogFactory

From source file de.escidoc.core.test.security.client.PWCallback.java

/**
 * PWCallback for the Client.<p/>
 * <p/>
 * Sets the eSciDoc user handle as the password if the technical username "eSciDocUser" is provided when calling the
 * webservice.<br> This password can be changed by using the <code>setHandle</code> and reset by using the
 * <code>resetHandle</code> methods

From source file wssec.TestWSSecurityWSS199.java

/**
 * A test-case for WSS-199 - "Add support for WCF non-standard Username Tokens"
 * (see also WSS-148 - "WCF interop issue: Namespace not honored incase of attributes.").
 * The issue is that WCF generated Username Tokens where the password type is namespace
 * qualified (incorrectly). WSS-199 added the ability to process these Username Tokens.
 */

From source file org.apache.cxf.security.spring.ServerPasswordCallbackHandler.java

public class ServerPasswordCallbackHandler implements CallbackHandler, InitializingBean {
    private static final Logger LOG = LogUtils.getL7dLogger(ServerPasswordCallbackHandler.class);

    private AuthenticationManager authenticationManager;
    private boolean nestExceptions;
    private boolean logExceptions;

From source file com.flexive.core.security.PassiveCallbackHandler.java

/**
 * PassiveCallbackHandler has constructor that takes
 * a username and password so its handle() method does
 * not have to prompt the user for input.
 * Useful for server-side applications.
 *