| Interface and Description |
|---|
| com.entrust.toolkit.security.crypto.signature.ExtendedSignature
This feature is not compatible with all Java implementations.
|
| com.entrust.toolkit.security.arithmetic.fields.Field
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.fields.FieldElement
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.exceptions.IExceptionWithCause
J2SE 1.4 makes this class redundant;
java.lang.Throwable
now contains Throwable getCause() (since 7.2) |
| iaik.security.random.SeedGenListener
since 8.0; seeding is now handled automatically by Entrust's
SecureRandom implementations (random number generators); for
access to the PRNGs underlying seeding algorithm call
generateSeed() on the SecureRandom
instance. |
| Class and Description |
|---|
| com.entrust.toolkit.asn1.structures.AlgorithmIdentifier
Use AlgorithmID instead (since JTK 7.0)
|
| com.entrust.toolkit.security.provider.AnsiRandom
since 7.0; use
X9_31usingAES256
instead |
| com.entrust.toolkit.asn1.structures.Cast5MacParameters
This class will never need to be used; it is intended for use with
the JCA Mac cryptographic algorithms, which do not accept
AlgorithmParameters at any API (since 7.0)
|
| com.entrust.toolkit.asn1.structures.Cast5MacParameterSpec
This is not a complete implementation, it does not provided ASN1
encoding/decoding; use CAST128MacParameterSpec instead (since 7.0)
|
| com.entrust.toolkit.security.spec.CAST5ParameterSpec
As of JTK 6.0; Use the class
iaik.security.cipher.CAST128ParameterSpec
|
| com.entrust.toolkit.x509.extensions.CertificateIssuer
As of JTK 6.0; Use the class iaik.x509.extenstions.CertificateIssuer
|
| com.entrust.toolkit.asn1.structures.CertTemplateCMP
Use CertTemplate instead (since JTK 7.0)
|
| com.entrust.toolkit.asn1.structures.Controls
Use Controls instead (since JTK 7.0)
|
| com.entrust.toolkit.x509.extensions.DeltaCRLIndicator
As of JTK 6.0; Use the class iaik.x509.extenstions.CertificateIssuer
|
| com.entrust.toolkit.asn1.structures.DistributionPointName
As of version 7.0, there should be no need to use this class.
Note that its behaviour is probably not what is expected when the choice of
distribution point name is nameRelativeToCRLIssuer.
|
| com.entrust.toolkit.security.crypto.signature.DsaCapi
since 8.0; use
DsaWithSha1Signature
instead |
| com.entrust.toolkit.security.provider.ECDSAKeyFactory
since 7.2 SP2; use
EcKeyFactory
instead |
| com.entrust.toolkit.security.provider.ECDSAKeyPairGenerator
since 7.2 SP2; use
EcKeyPairGenerator
instead |
| com.entrust.toolkit.security.provider.ECDSAPrivateKey
since 7.2 SP2; use
EcPrivateKey
instead |
| com.entrust.toolkit.security.provider.ECDSAPublicKey
since 7.2 SP2; use
EcPublicKey
instead |
| com.entrust.toolkit.security.provider.ECParameters
since 7.2 SP2; use
EcParameterSpecWithName
instead |
| com.entrust.toolkit.security.arithmetic.groups.ellipticCurve.ECPoint
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.groups.ellipticCurve.ECPointFactory
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.groups.ellipticCurve.ECPointGFp
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.groups.ellipticCurve.EllipticCurve
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.provider.EntrustDSA
since 8.0; use
DsaWithSha1Signature
instead |
| com.entrust.toolkit.security.provider.EntrustDSA.Raw
since 8.0; use
DsaWithNoneSignature
instead |
| com.entrust.toolkit.security.provider.EntrustDSAImpl
since 8.0; use
DsaWithSha1Signature
instead |
| com.entrust.toolkit.security.provider.EntrustDSAPKCS11
since 8.0; use
DsaWithSha1Signature
instead |
| com.entrust.toolkit.security.provider.EntrustECDSA
since 7.2 SP2; use
EcdsaWithSha1Signature
instead |
| com.entrust.toolkit.security.provider.EntrustPKCS11
since 7.0; use
Entrust instead |
| com.entrust.toolkit.security.provider.EntrustRawDSAPKCS11
since 8.0; use
DsaWithNoneSignature
instead |
| com.entrust.toolkit.security.provider.EntrustRawECDSA
since 7.2 SP2; use
EcdsaWithNoneSignature
instead |
| com.entrust.toolkit.asn1.structures.Extension
Use V3Extension instead (since JTK 7.0)
|
| com.entrust.toolkit.security.arithmetic.fields.FieldElementFactory
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.fields.FieldFactory
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.fields.GFp
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.fields.GFpElement
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| iaik.security.mac.HMac
since 8.0; use
HMac instead |
| iaik.security.mac.HMacMd5
since 8.0; use
Md5HMac instead |
| iaik.security.mac.HMacSha
since 7.0; use
Sha1HMac instead |
| com.entrust.toolkit.x509.extensions.HoldInstructionCode
As of JTK 6.0; Use the class iaik.x509.extenstions.HoldInstructionCode
|
| com.entrust.toolkit.x509.extensions.InvalidityDate
As of JTK 6.0; Use the class iaik.x509.extenstions.InvalidityDate
|
| com.entrust.toolkit.x509.extensions.IssuingDistributionPoint
As of JTK 6.0; Use the class iaik.x509.extenstions.IssuingDistributionPoint
|
| com.entrust.toolkit.util.MacGenerator
use javax.crypto.Mac instead with algorithms 'DES-MAC',
'DESede-MAC', 'CAST128-MAC', and 'IDEA-MAC'; since 7.0
|
| iaik.security.rsa.Md2RSASignature
since 8.0; use
Md2RsaSignature
instead |
| iaik.security.md.Md5
since 7.0; use
MD5 instead |
| iaik.security.md.Md5Old
since 7.0; use
MD5 instead |
| iaik.security.rsa.Md5RSASignature
since 8.0; use
Md5RsaSignature
instead |
| iaik.security.random.MetaSeedGenerator
since 8.0; seeding is now handled automatically by Entrust's
SecureRandom implementations (random number generators); for
access to the PRNGs underlying seeding algorithm call
generateSeed() on the SecureRandom
instance. |
| com.entrust.toolkit.security.provider.NamedCurveFactory
since 7.2 SP2; use
EcParameterFactory
instead |
| com.entrust.toolkit.asn1.structures.PasswordBasedMacParameters
This class will never need to be used; it is intended for use with
the JCA Mac cryptographic algorithms, which do not accept
AlgorithmParameters at any API (since 7.0)
|
| com.entrust.toolkit.asn1.structures.PasswordBasedMacParameterSpec
This is not a complete implementation, it does not provided ASN1
encoding/decoding; use PasswordBasedMacParameterSpec instead (since 7.0)
|
| com.entrust.toolkit.pkcs11.PKCS11Types
Use the constants in
JNIPKCS11 instead; since JTK 7.0 |
| com.entrust.toolkit.asn1.structures.PKIHeader
as of 7.0, use
PKIHeader |
| com.entrust.toolkit.asn1.structures.PMACVALUE
Use PKMACValue instead (since JTK 7.0)
|
| com.entrust.toolkit.x509.testlets.PolicyConstraintsCertTestlet
as of the 7.0 toolkit. All this functionality is now
part of
CertificatePoliciesCertTestlet. |
| com.entrust.toolkit.security.arithmetic.groups.ellipticCurve.PolynomeECPoint
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.fields.Polynomial
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.security.arithmetic.fields.PolynomialField
since 8.0; use Entrust's new EC architecture
com.entrust.toolkit.security.crypto.ec instead |
| com.entrust.toolkit.asn1.structures.POPSigningKeyInputCMP
Use POPOSigningKeyInput instead (since JTK 7.0)
|
| com.entrust.toolkit.security.crypto.signature.RawDsaCapi
since 8.0; use
DsaWithNoneSignature
instead |
| com.entrust.toolkit.security.spec.RC2ParameterSpecVersion
Use Entrust's RC2ParameterSpec instead (since JTK 7.0)
|
| iaik.security.cipher.Rijndael
since 8.0; use
AesCipher
instead |
| iaik.security.rsa.RSASignature
since 8.0; use
RsaPkcs1v1_5Signature
instead |
| iaik.security.random.SecRandom
since 8.0; use
Entrust.getDefaultSecureRandomInstance()
instead |
| com.entrust.toolkit.security.provider.SeedGenerator
seeding is now handled automatically by Entrust's SecureRandom
implementations (random number generators); for access to the PRNGs
underlying seeding algorithm call
generateSeed() on
the SecureRandom instance. |
| iaik.security.random.SeedGenerator
since 8.0; seeding is now handled automatically by Entrust's
SecureRandom implementations (random number generators); for
access to the PRNGs underlying seeding algorithm call
generateSeed() on the SecureRandom
instance. |
| iaik.security.md.SHA
since 7.0; use
SHA1 instead |
| iaik.security.rsa.ShaRSASignature
since 8.0; use
Sha1RsaSignature
instead |
| com.entrust.toolkit.asn1.structures.SubjectPublicKeyInfo
Use PublicKeyInfo instead (since JTK 7.0)
|
| com.entrust.toolkit.asn1.structures.Time
Use ChoiceOfTime instead (since JTK 7.0)
|
| com.entrust.toolkit.asn1.structures.Validity
Use OptionalValidity instead (since JTK 7.0)
|
| com.entrust.toolkit.security.provider.X917Random
since 7.0; use
X9_31using3DES
instead |
| Exceptions and Description |
|---|
| com.entrust.toolkit.exceptions.PasswordException
this class is no longer used and will be removed in a future
Toolkit version.
|
| com.entrust.toolkit.exceptions.ProfileException
this class is no longer used an will be removed in a future
Toolkit version.
|
| iaik.security.random.RandomException
since 8.0; all algorithms that use this exception have been
deprecated and it is thus no longer required
|
| Field and Description |
|---|
| com.entrust.toolkit.capi.CertPropertyId.CERT_ENTRUST_CERT_DEFINITION_POLICY_CERT
use
CertPropertyId.EE_CERT_PROP_CERT_DEFINITION_POLICY_CERT
instead; since 8.0 |
| com.entrust.toolkit.capi.CertPropertyId.CERT_ENTRUST_POLICY_CERT
use
CertPropertyId.EE_CERT_PROP_POLICY_CERT instead; since 8.0 |
| com.entrust.toolkit.pkcs11.MechanismList.CKM_ECDSA_KEY_PAIR_GEN
use
MechanismList.CKM_EC_KEY_PAIR_GEN instead; since 7.2 SP2 |
| com.entrust.toolkit.credentials.CMPCredentialReader.DSASignature
as of JTK 7.0 the algorithm of the signing key pair is always
extracted from the user's policy settings.
|
| com.entrust.toolkit.credentials.CMPCredentialReader.ECDSASignature
as of JTK 7.0 the algorithm of the signing key pair is always
extracted from the user's policy settings.
|
| com.entrust.toolkit.roaming.EntrustFileContentType.entrustRoamingSLA
as of 8.0 patch. This was required for applications that used the
Single Login feature which is no longer supported. This will be removed in a
future release of the toolkit.
|
| com.entrust.toolkit.asn1.structures.AlgorithmID.SignatureAlgs.id_RSASAA_PSS
Replaced by id_RSASSA_PSS. id_RSASAA_PSS was used due to an error in RFC 4056 (and subsequently fixed via EID 7280)
|
| com.entrust.toolkit.security.provider.Initializer.MODE_TOKEN
since 7.2 patch; use
Initializer.MODE_NORMAL instead |
| com.entrust.toolkit.credentials.CMPCredentialReader.PKIX4Version
as of JTK 7.0 proto-PKIX is no longer supported; instead PKIX-CMP
is always used for communication with the Security Manager
|
| com.entrust.toolkit.credentials.CMPCredentialReader.PKIX5Version
as of JTK 7.0 proto-PKIX is no longer supported; instead PKIX-CMP
is always used for communication with the Security Manager
|
| com.entrust.toolkit.util.HttpManagerClient.PROTOCOL_PKIX4
proto-PKIX is no longer supported.
|
| com.entrust.toolkit.util.HttpsManagerClientJSSE.PROTOCOL_PKIX4
proto-PKIX is no longer supported.
|
| com.entrust.toolkit.credentials.CMPCredentialReader.RSASignature
as of JTK 7.0 the algorithm of the signing key pair is always
extracted from the user's policy settings.
|
| Method and Description |
|---|
| com.entrust.toolkit.User.blockELILogout()
since 8.0; There is no longer a need to maintain this feature as
the Entrust Login Interface has been discontinued. This method will be removed in a
future release.
|
| com.entrust.toolkit.util.ByteArray.calculateASNLength()
this function was intended for internal JTK use only; deprecated
since 6.1
|
| com.entrust.toolkit.roaming.RoamingUser.changePassword(SecureStringBuffer, SecureStringBuffer)
As of 7.0, use
User.changePassword() with a
RoamingCredentialWriter object set to perform this task. |
| com.entrust.toolkit.util.ExtendedHasher.concatenate(byte[], byte[])
since 6.1; use
ByteArray.append(byte[])
instead |
| iaik.x509.X509CRL.containsCertificate(BigInteger)
use
X509CRL.containsCertificate(X509Certificate) This method is only useful
if a direct CRL is being used, an indirect CRL may contain multiple certificate issuers |
| com.entrust.toolkit.roaming.RoamingUser.create(String, SecureStringBuffer, CredentialCreator)
As of 7.0, use a
CredentialCreator with a
RoamingCredentialWriter object to perform this task. |
| com.entrust.toolkit.roaming.RoamingUser.deregister()
as of 7.0, the method
RoamingCredentialReader.deregister() should
be used to perform this function. |
| com.entrust.toolkit.pkcs11.TokenInfo.dualCryptoOperationsSupported()
use
isFlagSet( TokenInfo.CKF_DUAL_CRYPTO_OPERATIONS )
instead, since JTK 6.1 |
| com.entrust.toolkit.roaming.RoamingUser.encryptionKeyUpdateRequired()
As of 7.0, use a
RoamingCredentialReader and
RoamingCredentialWriter object with a User
object for key management tasks. |
| iaik.utils.CryptoUtils.extGcd(int, int)
use NumberTheory.extGcd() instead
|
| iaik.utils.CryptoUtils.gcd(int, int)
use NumberTheory.gcd() instead
|
| com.entrust.toolkit.x509.policies.ClientSettings.getCAVersion()
as of 7.0, since there is no way to determine the CA version
|
| com.entrust.toolkit.KeyAndCertificateSource.getCertStore()
use getCertificateStore()
|
| com.entrust.toolkit.x509.extensions.EntrustVersInfo.getEntrustInfo() |
| iaik.x509.extensions.PolicyConstraints.getInhibitExplicitPolicy()
see getInhibitPolicyMapping()
|
| com.entrust.toolkit.capi.CryptKey.getKeyParameter(KeyParam)
use
CryptKey.getKeyParam(KeyParam) instead; since 8.0 |
| com.entrust.toolkit.credentials.UserConfigSettings.getLDAPReceiveTimeout()
The configuration settings available to classes that
implement the
LdapDirectory interface should be used. |
| iaik.security.provider.IAIK.getMd5()
since 8.0; use
MD5
instead |
| com.entrust.toolkit.pkcs11.SlotList.getNumberOfSlotLists()
use
SlotList.getNumberOfSlots() instead, since JTK 6.1 |
| iaik.security.spec.PBKDF2KeyAndParameterSpec.getPassword()
use getSecurePassword
|
| iaik.x509.X509CRL.getRevokedCertificate(BigInteger)
use
X509CRL.getRevokedCertificate(X509Certificate) instead |
| iaik.x509.X509CRL.getRevokedCertificates()
This returns a Set, which does not allow duplicates. Therefore, if an
indirect CRL is used, a revoked certificate with duplicate data for a different
issuer would get overwritten. Use
instead |
| com.entrust.toolkit.pkcs11.SlotList.getSlotListIDs()
use
SlotList.getSlotIDs() instead, since JTK 6.1 |
| iaik.utils.CryptoUtils.getStrongPrime(int, Random)
use NumberTheory.getStrongPrime() instead
|
| iaik.security.provider.IAIK.getUseOldMd5()
since 8.0; use
MD5
instead |
| com.entrust.toolkit.pkcs11.TokenInfo.hasProtAuthPath()
use
isFlagSet( TokenInfo.CKF_PROTECTED_AUTHENTICATION_PATH )
instead, since JTK 6.1 |
| com.entrust.toolkit.pkcs11.TokenInfo.isClockOnToken()
use
isFlagSet( TokenInfo.CKF_CLOCK_ON_TOKEN ) instead,
since JTK 6.1 |
| com.entrust.toolkit.pkcs11.MechanismList.isDSAKeyPairGenSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_DSA_KEY_PAIR_GEN )
instead |
| com.entrust.toolkit.pkcs11.MechanismList.isDsaSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_DSA )
instead |
| com.entrust.toolkit.pkcs11.TokenInfo.isLoginRequired()
use
isFlagSet( TokenInfo.CKF_LOGIN_REQUIRED ) instead,
since JTK 6.1 |
| com.entrust.toolkit.pkcs11.MechanismList.isMd2RsaPkcsAlgorithmSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_MD2_RSA_PKCS )
instead |
| com.entrust.toolkit.pkcs11.MechanismList.isMd5RsaPkcsAlgorithmSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_MD5_RSA_PKCS )
instead |
| iaik.x509.qualified.QualifiedCertificate.isQualifedCertificate(X509Certificate)
Use
QualifiedCertificate.isQualifiedCertificate(X509Certificate); since 7.2 |
| com.entrust.toolkit.pkcs11.TokenInfo.isRestoreKeyNotNeeded()
use
isFlagSet( TokenInfo.CKF_RESTORE_KEY_NOT_NEEDED )
instead, since JTK 6.1 |
| iaik.x509.X509CRL.isRevoked(BigInteger) |
| com.entrust.toolkit.pkcs11.TokenInfo.isRNGSupported()
use
isFlagSet( TokenInfo.CKF_RNG ) instead, since JTK 6.1 |
| com.entrust.toolkit.pkcs11.MechanismList.isRsa9796AlgorithmSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_RSA_9796 )
instead |
| com.entrust.toolkit.pkcs11.MechanismList.isRsaKeyPairGenSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_RSA_PKCS_KEY_PAIR_GEN )
instead |
| com.entrust.toolkit.pkcs11.MechanismList.isRsaPkcsAlgorithmSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_RSA_PKCS )
instead |
| com.entrust.toolkit.pkcs11.MechanismList.isRsaX509AlgorithmSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_RSA_X_509 )
instead |
| com.entrust.toolkit.pkcs11.MechanismList.isSha1DsaSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_DSA_SHA1 )
instead |
| com.entrust.toolkit.pkcs11.MechanismList.isSha1RsaPkcsAlgorithmSupported()
use
MechanismList.hasMechanism( MechanismList.CKM_SHA1_RSA_PKCS )
instead |
| com.entrust.toolkit.pkcs11.TokenInfo.isUserPINInitialized()
use
isFlagSet( TokenInfo.CKF_USER_PIN_INITIALIZED )
instead, since JTK 6.1 |
| com.entrust.toolkit.pkcs11.TokenInfo.isWriteProtected()
use
isFlagSet( TokenInfo.CKF_WRITE_PROTECTED ) instead,
since JTK 6.1 |
| iaik.x509.X509CRL.listCertificates()
use listDerEncodedCertificates() where each element represents a
DER encoded byte array.
|
| com.entrust.toolkit.Trustmanager.load(User)
use the
Trustmanager(KeyAndCertificateSource source) constructor instead. |
| com.entrust.toolkit.roaming.RoamingUser.login(String, SecureStringBuffer)
as of 7.0,
RoamingCredentialReader and
RoamingCredentialWriter should be used with a User
object to perform this function. |
| com.entrust.toolkit.util.ManagerTransport.readPKIX4Response(boolean)
proto-PKIX protocol is no longer supported in the Toolkit. Always
use PKIX-CMP.
|
| com.entrust.toolkit.util.ManagerTransportWithSMProxy.readPKIX4Response(boolean) |
| com.entrust.toolkit.roaming.RoamingUser.recover(String, SecureStringBuffer, CredentialRecoverer)
As of 7.0, use a
CredentialRecoverer with a
RoamingCredentialWriter object to perform this task. |
| iaik.x509.X509CRL.removeCertificate(BigInteger)
Use method
X509CRL.removeCertificate(X509Certificate) instead |
| iaik.utils.CryptoUtils.resizeArray(byte[], int)
Use the method in iaik.utils.Util instead.
|
| com.entrust.toolkit.util.ManagerTransport.setClientCredentials(X509Certificate, X509Certificate, PrivateKey) |
| com.entrust.toolkit.util.ManagerTransportWithSMProxy.setClientCredentials(X509Certificate, X509Certificate, PrivateKey) |
| iaik.asn1.structures.AVA.setEncoding(ASN)
this method never performed any function; use
AVA(ObjectID, Object, ASN) instead |
| iaik.utils.Util.setEncoding(String)
since 8.0; by default 'US-ASCII' is used which (according to
Sun) must be supported by all implementations of the Java 2
platform, Standard Edition, v. 1.3 or higher
|
| iaik.x509.extensions.PolicyConstraints.setInhibitExplicitPolicy(int)
see setInhibitPolicyMapping()
|
| com.entrust.toolkit.credentials.UserConfigSettings.setLDAPReceiveTimeout(int)
The configuration settings available to classes that
implement the
LdapDirectory interface should be used.
For example, when a JNDIDirectory
object is used, it contains a
JNDIDirectory.setConnectionTimeout(int)
method that may be used to configure a timeout value. |
| com.entrust.toolkit.x509.directory.JNDIDirectory.setMaxConcurrentSearches(int)
no longer required since the search timeout is now controlled
by the "com.sun.jndi.ldap.read.timeout" value. This JNDI read timeout value
has the same effect as the "search" timeout value used by the toolkit. If there
is a problem when a search is done then it will time out based on the value of
the
JNDIDirectory.setSearchTimeout(int). |
| com.entrust.toolkit.x509.revocation.CollectionRS.setMaximumCRLLifetime(int)
all CRLs are required to have their
nextUpdate field set
(since 6.1 SP1) |
| com.entrust.toolkit.xencrypt.core.Encryptor.setTrustmanager(User)
use setTrustmanager(
Trustmanager trustmanager) instead. |
| iaik.security.provider.IAIK.setUseOldMd5(boolean)
since 8.0; use
MD5
instead |
| com.entrust.toolkit.roaming.RoamingUser.signingKeyUpdateRequired()
As of 7.0, use a
RoamingCredentialReader and
RoamingCredentialWriter object with a User
object for key management tasks. |
| com.entrust.toolkit.util.ExtendedHasher.tail(byte[], int)
since 6.1; use
ByteArray.tail(int) instead |
| com.entrust.toolkit.util.SecureStringBuffer.toASCIIByteArray()
use
toUSASCIIByteArray() instead; since 7.0patch |
| com.entrust.toolkit.util.ByteArray.toByte(int)
has the same effect as a direct cast, please use this instead,
ex: byte b = (byte)-234823; deprecated since 6.1
|
| com.entrust.toolkit.util.ByteArray.toInt(byte)
this function was intended for internal JTK use only; deprecated
since 6.1
|
| com.entrust.toolkit.util.ExtendedHasher.truncate(byte[], int)
since 6.1; use
ByteArray.truncate(int) instead |
| com.entrust.toolkit.User.unblockELILogout()
since 8.0; There is no longer a need to maintain this feature as
the Entrust Login Interface has been discontinued. This method will be removed in a
future release.
|
| com.entrust.toolkit.roaming.RoamingUser.updateEncryptionKeys()
As of 7.0, use a
RoamingCredentialReader and
RoamingCredentialWriter object with a User
object, and let the User perform key management automtically. |
| com.entrust.toolkit.roaming.RoamingUser.updateSigningKeys()
As of 7.0, use a
RoamingCredentialReader and
RoamingCredentialWriter object with a User
object, and let the User perform key management automtically. |