Hi Martin,
let me summarize what is currently supported and possible for EEM authentication:
1. EEM SAPGUI scripts
Here EEM only supports user/password authentication. Technically, SNC communication might be feasible as well and we were able to use it in a POC in the EEM Editor (by specifying additional connection parameters), but there are two major aspects that keep us from supporting it:
a. SNC depends on additional security libraries to implement SNC. In my understanding there are multiple vendors providing such a solution. Would be a huge effort even to set this up in a test environment.
b. Connection to the OS user: the certificate store for SNC is typically connected to the OS user. This would be the Windows Service user running the diagnostics agent, e.g. SAPServiceDAA. This does not fit to the concept of deploying multiple different self-contained script configurations including authentication to a robot.
2. EEM HTTP scripts
We should distinguish authentication and encryption here.
a. Encryption: EEM relies on the encryption features for HTTPS of the underlying SAP JVM 6 on robot side. Every script can have a dedicated list of trusted certificates. Using HTTPS should be sufficient to avoid sendind passwords in clear text over the network.
b. Authentication: Here I repeat the contents of the FAQ. Supported authentication methods:
* Basic
* NTLM
* X509 client certificates (provided in a script-specific key store)
Hope this clarifies it.
regards
Jens