PHP SOAP Client with WSSE
Budget: €250 – €750 EUR
I need a small, self-contained PHP script that can successfully call the helloWorldWithCertificate operation exposed in the WSDL at
https://brugerdatabasen.stil.dk/bpi/wsieksport/7?wsdl
Scope
• Build a SoapClient wrapper (PHP 8.4) that injects WSSE-Security headers (certificate + signature) exactly as required by the service.
• Use the certificates I already possess for production, but set the code up with separate, easily swappable test certificates. I can share only the public testing files; the private production keys will never leave my side.
• You will receive limited access to our staging endpoint for live verification.
• Basic logging and error handling is all that’s needed—write errors to a simple flat file or the PHP error log and echo the success response for the demo call.
Deliverables
1. PHP class / script, fully commented, that:
– Reads a .pfx or .pem key pair from disk,
– Adds Timestamp and BinarySecurityToken,
– Signs the request body,
– Calls helloWorldWithCertificate and prints the response.
2. Read-me with setup instructions: where to place keys, how to switch between test and production certificates, and any PHP extensions required (OpenSSL, Soap, etc.).
3. A short test video or screenshot proving the call succeeds against my test environment.
View SOAPUI definitions (danish) at : https://viden.stil.dk/spaces/INFRA2/pages/314540219/Certifikatsikkerhed
Keep dependencies minimal—if you prefer RobRichards/wsse-php or a similar library, note the exact version and include installation commands.
Once I confirm the call executes correctly with my own keys, the job is complete.
Test certificates should be acquired and provided for development purposes to ensure functionality can be verified without compromising production keys.
I have been using the PHP RobRichards classes without much luck. I don’t think they can be used without changes.
https://brugerdatabasen.stil.dk/bpi/wsieksport/7?wsdl
Scope
• Build a SoapClient wrapper (PHP 8.4) that injects WSSE-Security headers (certificate + signature) exactly as required by the service.
• Use the certificates I already possess for production, but set the code up with separate, easily swappable test certificates. I can share only the public testing files; the private production keys will never leave my side.
• You will receive limited access to our staging endpoint for live verification.
• Basic logging and error handling is all that’s needed—write errors to a simple flat file or the PHP error log and echo the success response for the demo call.
Deliverables
1. PHP class / script, fully commented, that:
– Reads a .pfx or .pem key pair from disk,
– Adds Timestamp and BinarySecurityToken,
– Signs the request body,
– Calls helloWorldWithCertificate and prints the response.
2. Read-me with setup instructions: where to place keys, how to switch between test and production certificates, and any PHP extensions required (OpenSSL, Soap, etc.).
3. A short test video or screenshot proving the call succeeds against my test environment.
View SOAPUI definitions (danish) at : https://viden.stil.dk/spaces/INFRA2/pages/314540219/Certifikatsikkerhed
Keep dependencies minimal—if you prefer RobRichards/wsse-php or a similar library, note the exact version and include installation commands.
Once I confirm the call executes correctly with my own keys, the job is complete.
Test certificates should be acquired and provided for development purposes to ensure functionality can be verified without compromising production keys.
I have been using the PHP RobRichards classes without much luck. I don’t think they can be used without changes.