Pasargad driver | resovles #13

[Keivan-sf]

resolves #13

The Pasargad driver and it's Api are implemented via Pasargad documents , Pasargad SKDs , Pasargad Swagger and the unit tests are provided.

However, I can say with confidence, even though I've surfed through the pasargad documentation and every sdk of this bank, this driver is likely to fail while interacting with the real api and there are several reasons for it:

• Swagger examples are not in agreement with documents examples
• SDK's are not in agreement with each other (There are differences between PHP and Nodejs SDK and so on ...)
• From how it looks, Pasargad Official Nodejs SDK will fail in real tests and is likely to have been never tested before
• Some properties are not even considered in the SDK's, but mentioned in the documentation

Anyway, I'm trying to contact their developer of the Nodejs SDK and get some pull requests merged to fix it.

This driver is built upon the most used SDK (php sdk) and the documentation but still I am not sure what Pasargad has in store for us. I guess we'll never know until someone tests it IRL.

The current problems:

• Pasargad, due to the examples, doesn't provide any error codes. so the error messages are all the same
• PrivateKey is provided as an rsa-xml file by Pasargad, while the driver needs the pem version. So the developers have to convert it in order to use the driver (Via libraries or online converters). I was unable to find a reliable way to convert them in driver
• There is no exception if the signing process fails (this applies to other drivers as well). And the crypto errors are inconvenient for a developer who does not know about the signing process

I'll submit and track the problems in issues section.

Sorry for the long description