Hi all, As I’m currently implementing the first drivers that require authentication, I was thinking of how we can make that integrate with third party systems.
Currently we have two getConnection methods. One without any Authentication and one that accepts Authentication. However, we have no way to guide a third party tool to what types of Authentication a given combination of Protocol and Transport requires. With Beckhoff AMS for example: * Plain AMS doesn’t need Authentication * Secure-AMS (PSK) requires a set of „Identity“ and „Password“ or „Identity“ and „Key“) * Secure-AMS (CA) requires a Java Keystore * Secure-AMS (Self-Signed) requires a Java Keystore plus an Admin username and password. I would say that the last option wouldn’t make sense to have in the public SPI parts as it’s totally dependent on the Driver. However the normal PSK and CA TLS options would make sense to have the Authentication type shipped along with the transport. So I was thinking … the way we currently also have „supported transports“ for the driver … it would make sense to have the same on both the driver and the transport to supply supported authentication interfaces. The implementations could use the same Annotations our config types use and self-describe themselves. What do you think? Chris
