J2EE Content Decryptor

SAP J2EE stores encrypted XML files or passwords in the VBYTES or FBLOB fields of the J2EE_CONFIGENTRY table. The encrypted content typically exceeds 26 bytes and begins with 0x01, followed by another byte ranging from 0x01 to 0x05, indicating the cryptographic version.

Below is an example of a query in MS SQL Server to retrieve passwords for the HTTP and RFC destinations in NWA:

/**
    *** NWA Destinations
    ***/
    DECLARE @SCHEMA VARCHAR(10);
    SELECT TOP 1 @SCHEMA = name FROM sys.schemas
     WHERE name LIKE 'SAP___DB';
    EXECUTE AS USER = @SCHEMA;

    -- HTTP passwords are stored in FBLOB
    SELECT CPATH, NAME, FBLOB
      FROM J2EE_CONFIG C 
           INNER JOIN J2EE_CONFIGENTRY CE
        ON C.CID = CE.CID
     WHERE SUBSTRING(FBLOB,1,1) = CHAR(1)
       AND SUBSTRING(FBLOB,2,1) BETWEEN CHAR(1) and CHAR(5) 
       AND CPATH LIKE 'destinations/sap_j2eeenginehttpdestination/%'
     ORDER BY 1, 2

    -- RFC passwords are stored in VBYTES
    SELECT CPATH, NAME, VBYTES
      FROM J2EE_CONFIG C 
           INNER JOIN J2EE_CONFIGENTRY CE
        ON C.CID = CE.CID
     WHERE SUBSTRING(VBYTES,1,1) = CHAR(1)
       AND SUBSTRING(VBYTES,2,1) BETWEEN CHAR(1) and CHAR(5) 
       AND CPATH LIKE 'destinations/RFC/%' 
     ORDER BY 1, 2

These passwords are encrypted using a key phrase found in the SecStore.key file. The key phrase is essential for decrypting the stored content. Utilize the J2EE SecStore File Decryptor to decode the key phrase and access the encrypted content.