v2.4.0

• Remove WsTargetId. It does not have to be visible on API side. For nordea, the API takes care of fetching TargetId parameter with bank side APIs. This happens after initial cert enrollment/import and with first files API call.
• Add pop to supported banks, was missing from documentation

v2.3.1

• Fix wstargetid caseness WsTargetId
• Improve documentation

v2.3.0

• uploadFile fixed and working now with authorize registered PGP detached ASCII armored signatures. Currently only one valid signature is required, but n/m schemes are possible in the future. Multiple PGP keys can be registered (either authorize or export) and multiple concatenated PGP detached ASCII armored signatures provided. API will go through all signatures and all valid authorize PGP keys and find out the number of valid signatures. If more than 1, then file is uploaded to bank.
• IntegratorTBDApi -> IntegratorApi
• PgpTBDAp --> PgpApi

v2.2.5

• Make PgpApi as PgpTBDApi
• Add IntegratorTBDApi
• More API parameter descriptions and examples

v2.2.4

• Two types of PGP keys, for export and for authorization. Only export keys can be used to export WS-Channel certificate and corresponding private key.
• Support for disabling private key export via ConfigCerts. When disabled, it can not be re-enabled via API (contact support if you need cert and private key export after that). Safety measure.
• Improve parameter descriptions

v2.2.3

• Update member names in ListCertsResp and ExportCertResp datatypes
• Update version to match GitHub release

v2.2.2

• API handles pgpList, pgpAdd, and pgpDelete calls and checks arguments. However, pgpAdd and pgpDelete are not doing anything else at the moment.

v2.2.1

• AWS API Gateway mapped error responses, e.g.

{
    "ResponseCode": "01",
    "ResponseText": "Invalid API key",
    "RequestId": "d11a9282-77a8-11e7-b7af-b3b9b93796d4"
}

v2.2.0

• Add session logout support that logs selected account mode user out. Note however, that AWS Cognito does NOT invalidate the idtoken (authorization) at the moment. Hopefully, they fix this soon.

v2.1.1

• ListCerts now provides certificate details and the certificate itself in PEM format