We have developed a view for our customers to manually upload their KSeF certificate and private key after generating it in your portal. However, our long-term goal is to offer a seamless, integrated solution that eliminates the need for manual file uploads, allowing users to complete the process in a single, simple step.
To enhance the customer experience, we need to integrate both systems as described above. Could you please confirm if you support OAuth2 authorization for this certificate generation process? If so, kindly provide the following information to help us initiate the integration:
1. Two OAuth2 Client Credentials (one for our Test environment and one for Production)
2. Authorization Endpoint URL and details
3. Token Endpoint URL and details
4. Certificate Management API documentation (to fetch the customer's private key and certificate using the access token)
FYI: We know that you have a way to do this via customer's qualified, seal certificate private key pair to first get a KSeF token and continue with the CSR mechanism but this needed to be avoided as it not ethical for the customer to expose their qualified seal certificate and private key to a 3rd party, so we want to let the customer login via your system, and automate the manual intervention on downloading and uploading the files.
We have developed a view for our customers to manually upload their KSeF certificate and private key after generating it in your portal. However, our long-term goal is to offer a seamless, integrated solution that eliminates the need for manual file uploads, allowing users to complete the process in a single, simple step.
To enhance the customer experience, we need to integrate both systems as described above. Could you please confirm if you support OAuth2 authorization for this certificate generation process? If so, kindly provide the following information to help us initiate the integration:
FYI: We know that you have a way to do this via customer's qualified, seal certificate private key pair to first get a KSeF token and continue with the CSR mechanism but this needed to be avoided as it not ethical for the customer to expose their qualified seal certificate and private key to a 3rd party, so we want to let the customer login via your system, and automate the manual intervention on downloading and uploading the files.