When you use a batch-server or connect-server with a SAS EIP installation we noticed that there is no authentication (password validation to metadata server) done.
It uses the OS user-id as the identified user and proceeds with that one as the metadata context.
There is no IWA configured. It is Unix environment.
The WS is setup as host-authentication. With that one, you have to specify the OS user twice. Once for the metadata connection and another following after that for the OS SAS session.
The last one gets cached (stored possible to be breached) in the SAS metadata. This is different as the batch/connect server. A strange difference between those two
Anyone found some information this is how it is designed and that it should work that way. Underpinning compliancy reasons.
---->-- ja karman --<-----