Age | Commit message (Collapse) | Author | Files | Lines |
|
The check can be disabled by using the configuration property: modules.sl20.security.truststore.need.valid.certificate
|
|
initialization
|
|
|
|
|
|
|
|
serializable
|
|
|
|
serialization for storage
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
INFO:
SSL Client-Authentication with keys from HSM-Facade only works with
BCJSSE Provider >= 1.70 and SystemD Parameter: -Dorg.bouncycastle.jsse.client.acceptRenegotiation=true
if HTTP Server requires re-negotiation.
Hint: do not enable SSL Debugging in BCJSSE Probider, because it throws
a NullPointerException with HSM-Facade keys!!!!
|
|
|
|
factory
|
|
|
|
|
|
'AuthenticatedEncryptionPendingRequestIdGenerationStrategy' that allows generation of already expired tokens
|
|
|
|
|
|
does not responde
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|