I had a look for the API NG login process. There are two ways:
1) Interactive desktop login.
The simple and excellent method. There is some pretty visual stuff, but it is pretty optional. In fact, "interactive" login works excellent in non-interactive way:
That's MacOSX/Linux but it is pretty the same for Windows
file out.txt contains line like this
The ssoid is modified, don't try it
2) non-interactive bot login
I didn't try the whole process, it is really complicated. Client check betfair is betfair and betfair checks client is client. It is openSSL based, requires key generation, certificate signing request, certificate itself, creating PEM file that has both key and certificate and uploading it to a magic URL.
The stuff really seems complex, it requires installing OpenSSL on Windows (on Linux/MacOSX it is installed in most of distributions).
Self-signed certificates are not great security stuff, everybody can upload it knowing BF login/password. There are much simpler systems based on uploading public keys, for example GitHub probably has the best one, generating key and upload it is a pleasure. By the way, I recommend github client for windows, it has exellent bash shell with full openSSL stuff there.
I think, Betfair can consider less brainwashing procedure, like, for example, github.com has. Github uses SSH protocol with certificates and standard HTTP auth for HTTPS (which is also much simpler).
If I am allowed to use "interactive" login procedure for bots, I will certainly do. The HTTPS encryption is enough for me
1) Interactive desktop login.
The simple and excellent method. There is some pretty visual stuff, but it is pretty optional. In fact, "interactive" login works excellent in non-interactive way:
Code:
curl -v -c cookies.txt -d "username=Username&password=password&login=true&redirectMethod=POST&product=home.betfair.int&url=https://www.betfair.com/" https://identitysso.betfair.com/api/login >out.txt 2>&1
file out.txt contains line like this
Code:
< Set-Cookie: ssoid=xm2dfD3dbc/ZR9S43gXVgRJ1fWLuigkN9vzR28LbpnRH=; Domain=.betfair.com; Path=/
2) non-interactive bot login
I didn't try the whole process, it is really complicated. Client check betfair is betfair and betfair checks client is client. It is openSSL based, requires key generation, certificate signing request, certificate itself, creating PEM file that has both key and certificate and uploading it to a magic URL.
The stuff really seems complex, it requires installing OpenSSL on Windows (on Linux/MacOSX it is installed in most of distributions).
Self-signed certificates are not great security stuff, everybody can upload it knowing BF login/password. There are much simpler systems based on uploading public keys, for example GitHub probably has the best one, generating key and upload it is a pleasure. By the way, I recommend github client for windows, it has exellent bash shell with full openSSL stuff there.
I think, Betfair can consider less brainwashing procedure, like, for example, github.com has. Github uses SSH protocol with certificates and standard HTTP auth for HTTPS (which is also much simpler).
If I am allowed to use "interactive" login procedure for bots, I will certainly do. The HTTPS encryption is enough for me


Comment