Age | Commit message (Collapse) | Author | Files | Lines |
|
The keystore type 'inline' can be used to build a keystore by using
PEM encoded certificate and key files.
Example: pkcs12:keystore?private=certs/key.pem&cert=certs/certificate.pem
|
|
|
|
|
|
|
|
wrote log messages on level 'debug' if no message property was found
|
|
pendingRequestId's
|
|
|
|
|
|
|
|
factory
|
|
|
|
|
|
'AuthenticatedEncryptionPendingRequestIdGenerationStrategy' that allows generation of already expired tokens
|
|
|
|
|
|
deadline, see https://grpc.io/blog/deadlines/
|
|
|
|
|
|
Use custom SSLContext builder to generate BouncyCastle specific TrustManager...
See merge request egiz/eaaf_components!23
|
|
|
|
in case of keys base on HSM-Facade, because SSLContext based on BCJSSE needs BCJSSE TrustManager
BCJSSE is not compatible to SunJSSE TrustManager in Java >= 9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from pool
|
|
|
|
with signature-verification and lost configuration states
|
|
|
|
|
|
|
|
|
|
|
|
specific implementation in other classes
|
|
|
|
|
|
Shibboleth IDP implementation
|
|
|
|
authenticated-encryption protect the internal pendingRequesttId
|
|
Security-Provider
|
|
passphrase based symmetric keys and keys from HSM-Facade
|