Thanks Julius for your response,
We did try this already, but it doesn’t work in our setup.
A short technical description:
You need an accessor after this getInstance().newConnection to check it against a collection. Now if you do this on the collection ino:security and the password validation fails, then the request is handled by the java.net.Authenticator. (We use the authenticator for gaining access with an elevated privilege) .
In that case the Tamino API apparently falls back by triing authentication on port 80, which, succeeds while it should not.
So we need another way. Can we encrypt the password ourselves to check it against the stored password?
Kees
#API-Management#webMethods-Tamino-XML-Server-APIs#webMethods