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.wso2.am.integration.test.utils.common.utils.clients.SecureAxisServiceClient.java

public class SecureAxisServiceClient implements CallbackHandler {
    private static final Log log = LogFactory.getLog(SecureAxisServiceClient.class);

    /**
     * This will send request by getting keyStore wso2carbon.jks
     *

From source file wssec.SignatureKeyValueTest.java

/**
 * This class tests signing where the the public key is transmitted in the message via
 * a ds:KeyInfo/ds:KeyValue element. Although this isn't strictly recommended for use in
 * WS-Security, it's necessary to support it for WCF interop.
 */
public class SignatureKeyValueTest extends TestCase implements CallbackHandler {

From source file wssec.TestWSSecurityNew15.java

/**
 * Test that encrypt and decrypt a WS-Security envelope.
 * 
 * This test uses the RSA_15 algorithm to transport (wrap) the symmetric key.
 * The test case creates a ReferenceList element that references EncryptedData
 * elements. The ReferencesList element is put into the Security header, not

From source file wssec.TestWSSecurityWSS178.java

/**
 * WS-Security Test Case for WSS-178 - "signature verification failure of signed saml token due to "
 * "The Reference for URI (bst-saml-uri) has no XMLSignatureInput".
 * 
 * The problem is that the signature is referring to a SecurityTokenReference via the STRTransform,
 * which in turn is referring to the SAML Assertion. The request is putting the SAML Assertion

From source file wssec.TestWSSecurityWSS86.java

/**
 * This is a test for WSS-86 - "CryptoBase.splitAndTrim does not take into account the format of a 
 * DN constructed by different providers":
 * http://issues.apache.org/jira/browse/WSS-86
 * 
 * Keystore: keys\wss86.keystore

From source file wssec.TestWSSecuritySAMLKeyIdentifier.java

/**
 * Test-case for checking KeyIdentifier (and not Reference) elements 
 * are used to identify SAML tokens
 * 
 */
public class TestWSSecuritySAMLKeyIdentifier extends TestCase implements CallbackHandler {

From source file wssec.TestWSSecurityNew2.java

/**
 * WS-Security Test Case
 * <p/>
 * 
 * @author Davanum Srinivas (dims@yahoo.com)
 */

From source file wssec.TestWSSecurityDataRef.java

/**
 * Test that checks for correct WSDataRef which should be returned by 
 * <code>org.apache.ws.security.processor.ReferenceListProcessor</code> 
 * 
 * This test uses the RSA_15 algorithm to transport (wrap) the symmetric key.
 * The test case creates a ReferenceList element that references EncryptedData

From source file org.wso2.carbon.integration.common.utils.clients.SecureAxisServiceClient.java

/**
 * Security service client for invoking secured services
 */
public class SecureAxisServiceClient implements CallbackHandler {
    private static final Log log = LogFactory.getLog(SecureAxisServiceClient.class);

From source file wssec.TestWSSecurityDataRef1.java

/**
 * Test that checks for correct WSDataRef which should be returned by 
 * <code>org.apache.ws.security.processor.EncryptedKeyProcessor</code> 
 * 
 * This test uses the RSA_15 algorithm to transport (wrap) the symmetric key.
 * The test case creates a ReferenceList element that references EncryptedData