API changes - Java Server
- S (Deactivated)
New functionality
PAdES support
The 5.2 version of BankID J Server introduces new varaiables to the BIDSessionData class. The new variables provide the possibility to specify CMS (PKCS#7) and OCSP response formats to be used during a Sign operation. The new formats are introduced to enable creation of PAdES compatible PDF Signatures, and should generally not be used in other signing scenarios.
Authentication transactions will allways use the original default BankID formats. Any formats set in BIDSessionData will be ignored for such transactions.
The formats must be set in the session data before calling initTransaction. They will be passed along to the COI through the web client, and will also be used in BankID J Server during verifyTransactionRequest.
Details about the new enum classes and their values, and the changes to BIDSessionData, can be found in the subsequent sections.
CMSFormat (Enum)
Value | Description |
|---|---|
PKCS7 | The original default format in BankID. Not compatible with PAdES |
PKCS7_ISO320001 | Format conforming to ISO320001. Compatible with PAdES |
OCSPFormat (Enum)
Value | Description |
|---|---|
OCSP_BANKID_DEFAULT | The original default format in BankID. Not compatible with PAdES |
OCSP_RFC6960_COMPATIBLE | Format conforming to RFC 6960. Compatible with PAdES |
BIDSessionData
Variable | Type | Description |
|---|---|---|
cmsFormat | CMSFormat | The CMS format to be used during a Sign operation. Default value: CMSFormat.PKCS7 |
ocspFormat | OCSPFormat | The OCSP format to be used during a Sign operation. Default value: OCSPFormat.OCSP_BANKID_DEFAULT |
Removed functionality
Functionality related to BankID 1.0 has been discontinued. In relation to this discontinuation, the following functions have been removed in version 5.2:
- getTag
- getLauncherURI
Support for validating the legacy BankID SDO format has also been removed in version 5.2. This affects the method validateSDO, which from now on only supports validation of SEID SDO’s.