Hi. I am new to authorize.net development. I am trying to get SDK working with the "Hello World" example and it seems like the SDK is missing parts and it poorly setup for public use.
From the start the git page indicates:
"Composer currently has a MITM security vulnerability. However, if you wish to use it..."
So right away I don't want to use it: for the reason your developers has mentioned, and for general not wanting to include 3rd party apps to our secure app.
The other option is manual including autoloader, but that is missing files:
- JMS serilizer was missing, and there is no mention of it anywhere in the authorize documentation.
after fixing that I see it is again missing another dependency: phpcollection and again there is no mention of getting that in documentation.
I haven't spend time fixing the other dependency, but since none of these where mentioned in documentation, now I am doubting competency and reliablity of your product. Who knows howmany other dependencies is going to be there, even after I fix the next, and the next.
If any of the developers working for me, made a documentation like yours, or so much dependent on 3rd party code with known security volunability I would have a seriouse talk with them.
How to fix:
1 -first dicsiplin you team to not put incomple documentation live, and if they did, they don't continue defending incomeleteness after it has been brought to their attention on the forum.
2 -Add documentation about dependensies when SDK is used without composer.
3 -Do not rely on 3rd party library or program for your suppose-to-be-secure code.
