I don't want to kill your expectations but I would be very surprised if the switched supports those parameters.
Not only that, I have the same switch, v1, but the switch is not even capable of passing the port type (ethernet) to the RADIUS server.

Regarding the other behavior that you see:

Switch always said "Port authentication passed" but nothing happens and the next one message is "Port authentication exit".

I have the same problem with my Linux clients or any client that is not capable of running TP-Link propiertary 802.1x client software (basically any non-Windows client). As far as I could analyze the TP-Link 802.1x propietary client is sending the switch some kind of "heartbeat" packet around every 10 seconds. If the switch doesn't receive this heartbeat from the client (and no standard client -like the one native on Linux or even Windows- is capable of sending this non-standard customized packet as far as I know) after 20-30 seconds it will show the "Authentication exit" message and block the port.

This is very, very annoying, because 802.1x is basically useless on TP-Link switches unless 100% of your clients are running Windows and the propietary TP-Link client.

I just opened a support case about this, since I own two TP-Link switches (TL-SG3210 and TL-SG3424) and I'm experiencing the same behavior with both.

Once I get a response from TP-Link I will post any news here.

It's likely you are not running the TP-Link 802.1x client.

TP-Link switches will only work with clients using their 802.1x client for Windows. After opening a support case to them, they confirmed that the switch is incompatible with any other 802.1x implementation than their own 802.1x Windows client.

This is very sad since basically the switch will not able able to provide 802.1x security in any mixed environment with Mac or Linux clients.