ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

Credentials that never reach a script: HTTP, SOAP, mail, keystores, signatures

A stored username-and-password credential authenticates HTTP and SOAP clients, mail stores and mailers from a script without the script holding the password. XML signatures can embed the certificate.

A script that calls an external service needs a password. The question is whether the script ever sees it. After this release, it does not.

Stored and unwrapped in Java

  • A credential type for accounts An account name and an encrypted password stored as a third-party credential, for basic authentication and the like.
  • Clients take it whole The HTTP client's basic and digest authorisation, the SOAP client, the mail store and the mailer accept the stored credential or a protected password and decrypt inside Java. Any other type is rejected.
  • Keys from keystores A symmetric key is read from a JCEKS or PKCS12 keystore by a plain or protected entry password, and the AES helper takes any key, with encrypt and decrypt by key and vector.

Signatures

  • The certificate in the signature Enveloped and detached XML signers can embed the signing certificate, which most e-invoicing receivers require. The default is unchanged, so existing signatures are byte-identical.

Secrets are unwrapped in Java and never reach the script. That sentence is the whole release.