@alliander-opensource/aws-jwt-sts 0.3.3 → 0.3.5

package/node_modules/@aws-sdk/client-kms/dist-types/commands/SignCommand.d.ts

@@ -31,11 +31,11 @@ declare const SignCommand_base: {
  *         signature</a> for a message or message digest by using the private key in an asymmetric
  *       signing KMS key. To verify the signature, use the <a>Verify</a> operation, or use
  *       the public key in the same asymmetric KMS key outside of KMS. For information about asymmetric KMS keys, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html">Asymmetric KMS keys</a> in the <i>Key Management Service Developer Guide</i>.</p>
- *          <p>Digital signatures are generated and verified by using asymmetric key pair, such as an RSA
- *       or ECC pair that is represented by an asymmetric KMS key. The key owner (or an authorized
- *       user) uses their private key to sign a message. Anyone with the public key can verify that the
- *       message was signed with that particular private key and that the message hasn't changed since
- *       it was signed. </p>
+ *          <p>Digital signatures are generated and verified by using asymmetric key pair, such as an
+ *       RSA, ECC, or ML-DSA pair that is represented by an asymmetric KMS key. The key owner (or an
+ *       authorized user) uses their private key to sign a message. Anyone with the public key can
+ *       verify that the message was signed with that particular private key and that the message
+ *       hasn't changed since it was signed. </p>
  *          <p>To use the <code>Sign</code> operation, provide the following information:</p>
  *          <ul>
  *             <li>
@@ -48,8 +48,8 @@ declare const SignCommand_base: {
  *                <p>Use the <code>Message</code> parameter to specify the message or message digest to
  *           sign. You can submit messages of up to 4096 bytes. To sign a larger message, generate a
  *           hash digest of the message, and then provide the hash digest in the <code>Message</code>
- *           parameter. To indicate whether the message is a full message or a digest, use the
- *             <code>MessageType</code> parameter.</p>
+ *           parameter. To indicate whether the message is a full message, a digest, or an ML-DSA
+ *           EXTERNAL_MU, use the <code>MessageType</code> parameter.</p>
  *             </li>
  *             <li>
  *                <p>Choose a signing algorithm that is compatible with the KMS key. </p>
@@ -91,11 +91,11 @@ declare const SignCommand_base: {
  * const input = { // SignRequest
  *   KeyId: "STRING_VALUE", // required
  *   Message: new Uint8Array(), // e.g. Buffer.from("") or new TextEncoder().encode("")   // required
- *   MessageType: "RAW" || "DIGEST",
+ *   MessageType: "RAW" || "DIGEST" || "EXTERNAL_MU",
  *   GrantTokens: [ // GrantTokenList
  *     "STRING_VALUE",
  *   ],
- *   SigningAlgorithm: "RSASSA_PSS_SHA_256" || "RSASSA_PSS_SHA_384" || "RSASSA_PSS_SHA_512" || "RSASSA_PKCS1_V1_5_SHA_256" || "RSASSA_PKCS1_V1_5_SHA_384" || "RSASSA_PKCS1_V1_5_SHA_512" || "ECDSA_SHA_256" || "ECDSA_SHA_384" || "ECDSA_SHA_512" || "SM2DSA", // required
+ *   SigningAlgorithm: "RSASSA_PSS_SHA_256" || "RSASSA_PSS_SHA_384" || "RSASSA_PSS_SHA_512" || "RSASSA_PKCS1_V1_5_SHA_256" || "RSASSA_PKCS1_V1_5_SHA_384" || "RSASSA_PKCS1_V1_5_SHA_512" || "ECDSA_SHA_256" || "ECDSA_SHA_384" || "ECDSA_SHA_512" || "SM2DSA" || "ML_DSA_SHAKE_256", // required
  *   DryRun: true || false,
  * };
  * const command = new SignCommand(input);
@@ -103,7 +103,7 @@ declare const SignCommand_base: {
  * // { // SignResponse
  * //   KeyId: "STRING_VALUE",
  * //   Signature: new Uint8Array(),
- * //   SigningAlgorithm: "RSASSA_PSS_SHA_256" || "RSASSA_PSS_SHA_384" || "RSASSA_PSS_SHA_512" || "RSASSA_PKCS1_V1_5_SHA_256" || "RSASSA_PKCS1_V1_5_SHA_384" || "RSASSA_PKCS1_V1_5_SHA_512" || "ECDSA_SHA_256" || "ECDSA_SHA_384" || "ECDSA_SHA_512" || "SM2DSA",
+ * //   SigningAlgorithm: "RSASSA_PSS_SHA_256" || "RSASSA_PSS_SHA_384" || "RSASSA_PSS_SHA_512" || "RSASSA_PKCS1_V1_5_SHA_256" || "RSASSA_PKCS1_V1_5_SHA_384" || "RSASSA_PKCS1_V1_5_SHA_512" || "ECDSA_SHA_256" || "ECDSA_SHA_384" || "ECDSA_SHA_512" || "SM2DSA" || "ML_DSA_SHAKE_256",
  * // };
  *
  * ```

package/node_modules/@aws-sdk/client-kms/dist-types/commands/UpdatePrimaryRegionCommand.d.ts

@@ -33,7 +33,8 @@ declare const UpdatePrimaryRegionCommand_base: {
  *       in <code>us-east-1</code> and a replica key in <code>eu-west-2</code>. If you run
  *         <code>UpdatePrimaryRegion</code> with a <code>PrimaryRegion</code> value of
  *         <code>eu-west-2</code>, the primary key is now the key in <code>eu-west-2</code>, and the
- *       key in <code>us-east-1</code> becomes a replica key. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-update.html">Change the primary key in a set of multi-Region keys</a> in the <i>Key Management Service Developer Guide</i>.</p>
+ *       key in <code>us-east-1</code> becomes a replica key. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-update.html">Change the primary key in a
+ *         set of multi-Region keys</a> in the <i>Key Management Service Developer Guide</i>.</p>
  *          <p>This operation supports <i>multi-Region keys</i>, an KMS feature that lets you create multiple
  *       interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key
  *       material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt

package/node_modules/@aws-sdk/client-kms/dist-types/commands/VerifyCommand.d.ts

@@ -74,9 +74,9 @@ declare const VerifyCommand_base: {
  * const input = { // VerifyRequest
  *   KeyId: "STRING_VALUE", // required
  *   Message: new Uint8Array(), // e.g. Buffer.from("") or new TextEncoder().encode("")   // required
- *   MessageType: "RAW" || "DIGEST",
+ *   MessageType: "RAW" || "DIGEST" || "EXTERNAL_MU",
  *   Signature: new Uint8Array(), // e.g. Buffer.from("") or new TextEncoder().encode("")   // required
- *   SigningAlgorithm: "RSASSA_PSS_SHA_256" || "RSASSA_PSS_SHA_384" || "RSASSA_PSS_SHA_512" || "RSASSA_PKCS1_V1_5_SHA_256" || "RSASSA_PKCS1_V1_5_SHA_384" || "RSASSA_PKCS1_V1_5_SHA_512" || "ECDSA_SHA_256" || "ECDSA_SHA_384" || "ECDSA_SHA_512" || "SM2DSA", // required
+ *   SigningAlgorithm: "RSASSA_PSS_SHA_256" || "RSASSA_PSS_SHA_384" || "RSASSA_PSS_SHA_512" || "RSASSA_PKCS1_V1_5_SHA_256" || "RSASSA_PKCS1_V1_5_SHA_384" || "RSASSA_PKCS1_V1_5_SHA_512" || "ECDSA_SHA_256" || "ECDSA_SHA_384" || "ECDSA_SHA_512" || "SM2DSA" || "ML_DSA_SHAKE_256", // required
  *   GrantTokens: [ // GrantTokenList
  *     "STRING_VALUE",
  *   ],
@@ -87,7 +87,7 @@ declare const VerifyCommand_base: {
  * // { // VerifyResponse
  * //   KeyId: "STRING_VALUE",
  * //   SignatureValid: true || false,
- * //   SigningAlgorithm: "RSASSA_PSS_SHA_256" || "RSASSA_PSS_SHA_384" || "RSASSA_PSS_SHA_512" || "RSASSA_PKCS1_V1_5_SHA_256" || "RSASSA_PKCS1_V1_5_SHA_384" || "RSASSA_PKCS1_V1_5_SHA_512" || "ECDSA_SHA_256" || "ECDSA_SHA_384" || "ECDSA_SHA_512" || "SM2DSA",
+ * //   SigningAlgorithm: "RSASSA_PSS_SHA_256" || "RSASSA_PSS_SHA_384" || "RSASSA_PSS_SHA_512" || "RSASSA_PKCS1_V1_5_SHA_256" || "RSASSA_PKCS1_V1_5_SHA_384" || "RSASSA_PKCS1_V1_5_SHA_512" || "ECDSA_SHA_256" || "ECDSA_SHA_384" || "ECDSA_SHA_512" || "SM2DSA" || "ML_DSA_SHAKE_256",
  * // };
  *
  * ```

package/node_modules/@aws-sdk/client-kms/dist-types/endpoint/EndpointParameters.d.ts

@@ -3,12 +3,12 @@ import { Endpoint, EndpointParameters as __EndpointParameters, EndpointV2, Provi
  * @public
  */
 export interface ClientInputEndpointParameters {
-    region?: string | Provider<string>;
-    useDualstackEndpoint?: boolean | Provider<boolean>;
-    useFipsEndpoint?: boolean | Provider<boolean>;
+    region?: string | undefined | Provider<string | undefined>;
+    useDualstackEndpoint?: boolean | undefined | Provider<boolean | undefined>;
+    useFipsEndpoint?: boolean | undefined | Provider<boolean | undefined>;
     endpoint?: string | Provider<string> | Endpoint | Provider<Endpoint> | EndpointV2 | Provider<EndpointV2>;
 }
-export type ClientResolvedEndpointParameters = ClientInputEndpointParameters & {
+export type ClientResolvedEndpointParameters = Omit<ClientInputEndpointParameters, "endpoint"> & {
     defaultSigningName: string;
 };
 export declare const resolveClientEndpointParameters: <T>(options: T & ClientInputEndpointParameters) => T & ClientResolvedEndpointParameters;
@@ -31,8 +31,8 @@ export declare const commonParams: {
     };
 };
 export interface EndpointParameters extends __EndpointParameters {
-    Region?: string;
-    UseDualStack?: boolean;
-    UseFIPS?: boolean;
-    Endpoint?: string;
+    Region?: string | undefined;
+    UseDualStack?: boolean | undefined;
+    UseFIPS?: boolean | undefined;
+    Endpoint?: string | undefined;
 }

package/node_modules/@aws-sdk/client-kms/dist-types/index.d.ts

@@ -8,18 +8,20 @@
  *          <note>
  *             <p>KMS has replaced the term <i>customer master key (CMK)</i> with <i>KMS key</i> and <i>KMS key</i>. The concept has not changed. To prevent breaking changes, KMS is keeping some variations of this term.</p>
  *             <p>Amazon Web Services provides SDKs that consist of libraries and sample code for various programming
- *         languages and platforms (Java, Ruby, .Net, macOS, Android, etc.). The SDKs provide a
- *         convenient way to create programmatic access to KMS and other Amazon Web Services services. For example,
- *         the SDKs take care of tasks such as signing requests (see below), managing errors, and
- *         retrying requests automatically. For more information about the Amazon Web Services SDKs, including how to
- *         download and install them, see <a href="http://aws.amazon.com/tools/">Tools for Amazon Web
- *           Services</a>.</p>
+ *         languages and platforms (Java, Rust, Python, Ruby, .Net, macOS, Android, etc.). The SDKs
+ *         provide a convenient way to create programmatic access to KMS and other Amazon Web Services services.
+ *         For example, the SDKs take care of tasks such as signing requests (see below), managing
+ *         errors, and retrying requests automatically. For more information about the Amazon Web Services SDKs,
+ *         including how to download and install them, see <a href="http://aws.amazon.com/tools/">Tools
+ *           for Amazon Web Services</a>.</p>
  *          </note>
  *          <p>We recommend that you use the Amazon Web Services SDKs to make programmatic API calls to KMS.</p>
  *          <p>If you need to use FIPS 140-2 validated cryptographic modules when communicating with
- *       Amazon Web Services, use the FIPS endpoint in your preferred Amazon Web Services Region. For more information about the
- *       available FIPS endpoints, see <a href="https://docs.aws.amazon.com/general/latest/gr/kms.html#kms_region">Service endpoints</a> in the Key Management Service topic of
- *       the <i>Amazon Web Services General Reference</i>.</p>
+ *       Amazon Web Services, use one of the FIPS endpoints in your preferred Amazon Web Services Region. If you need communicate
+ *       over IPv6, use the dual-stack endpoint in your preferred Amazon Web Services Region. For more information
+ *       see <a href="https://docs.aws.amazon.com/general/latest/gr/kms.html#kms_region">Service
+ *         endpoints</a> in the Key Management Service topic of the <i>Amazon Web Services General Reference</i> and <a href="https://docs.aws.amazon.com/kms/latest/developerguide/ipv6-kms.html">Dual-stack endpoint
+ *         support</a> in the KMS Developer Guide.</p>
  *          <p>All KMS API calls must be signed and be transmitted using Transport Layer Security
  *       (TLS). KMS recommends you always use the latest supported TLS version. Clients must also
  *       support cipher suites with Perfect Forward Secrecy (PFS) such as Ephemeral Diffie-Hellman