I can verifiy that recently as of 4.25.2012 FirstData still has this problem when creating new SOAP or WebConnect 1.0 clients.
I have created 4 accounts brand new and every one of the downloaded certificates, passwords and pem files were not valid.
I was recieving the 401 Unauthrorized exception as well. And I can tell you this.
1) You need to make sure you install the WSXXXXXXXX._.1.p12 into your local certificate store. You need to use the p12.pw.txt when importing it.
2) You need to verify you have the host process permissions to access the WSXXXXXXX._.1.pem file.
3) When creating your connection make sure you use the WSXXXXXXXX._.1auth.txt and the store number.
If you see SSL/TTL error messages you are not leaving your machine. You need to ensure you have the certificate "p12 file" in your local computer installed correctly specifically the ._.1.p12 file with the correct permissions.
If you see anything about not establishing a connection. the process is not able to find your ._.1.pem file.
If you see a 401 unauthorized net exception. Time to call first data support because your certificates are bad and they need to regenerate them server side and repost them so you can download them.
NOTE: if you do have to have them regenerate your files. Please remove all reference of the previous tar files and remove the certificate from yoru local key store as well as remove the pem file.
I have literaly spent days of my life on the phone with these people.
Stagging is not like production. They have several issues that exist in staging or in production but not in stagging. Currently they do not support same day peroidic payments. You will need to address this by adding +1 days etc for testing.
They had could still have issues with the old HTTP protocol Expect100Continue flag. In production it is not used but in staging it was. They appear to have fixed that but if you continue to have issues it may be back in stagging. You set this when establishing
your connection. I externalized all these attributes and use injection based on my environment.
XMLViking
Member
452 Points
91 Posts
Re: First Data Web Service API Integration Problem
Apr 25, 2012 08:56 PM|LINK
I can verifiy that recently as of 4.25.2012 FirstData still has this problem when creating new SOAP or WebConnect 1.0 clients.
I have created 4 accounts brand new and every one of the downloaded certificates, passwords and pem files were not valid.
I was recieving the 401 Unauthrorized exception as well. And I can tell you this.
1) You need to make sure you install the WSXXXXXXXX._.1.p12 into your local certificate store. You need to use the p12.pw.txt when importing it.
2) You need to verify you have the host process permissions to access the WSXXXXXXX._.1.pem file.
3) When creating your connection make sure you use the WSXXXXXXXX._.1auth.txt and the store number.
If you see SSL/TTL error messages you are not leaving your machine. You need to ensure you have the certificate "p12 file" in your local computer installed correctly specifically the ._.1.p12 file with the correct permissions.
If you see anything about not establishing a connection. the process is not able to find your ._.1.pem file.
If you see a 401 unauthorized net exception. Time to call first data support because your certificates are bad and they need to regenerate them server side and repost them so you can download them.
NOTE: if you do have to have them regenerate your files. Please remove all reference of the previous tar files and remove the certificate from yoru local key store as well as remove the pem file.
I have literaly spent days of my life on the phone with these people.
Stagging is not like production. They have several issues that exist in staging or in production but not in stagging. Currently they do not support same day peroidic payments. You will need to address this by adding +1 days etc for testing.
They had could still have issues with the old HTTP protocol Expect100Continue flag. In production it is not used but in staging it was. They appear to have fixed that but if you continue to have issues it may be back in stagging. You set this when establishing your connection. I externalized all these attributes and use injection based on my environment.
Good luck.