No issues for server to server communication.
Regards
Sarav
On Fri, 4 Nov 2022 at 4:25 PM, Bjørn Nachtwey
wrote:
> Hi,
>
> does this new feature also affect the server2server communication, e.g.
> for LibMan <=> LibClient?
>
> If so, which server should I upgrade first? Or should I set all
> p
Hi,
does this new feature also affect the server2server communication, e.g.
for LibMan <=> LibClient?
If so, which server should I upgrade first? Or should I set all
passwords to UPCASE?
Thanks & best
Bjørn
On 02.11.22 17:22, Michael Prix wrote:
Hello Sarav,
not strange, but works as de
Hi Michael
Yes it works perfect. All passwords are auto converted to CAPS after upgrade to
v8.1.16.
Thanks for your inputs.
Regards
Sarav
+65 9857 8665
> On 3 Nov 2022, at 12:23 AM, Michael Prix wrote:
>
> Hello Sarav,
>
> not strange, but works as designed (by IBM).
> Introduced w
Hello Sarav,
not strange, but works as designed (by IBM).
Introduced with 8.1.16 is case sensitivity for the passwords.
So, if you send a command from a server with codelevel lower than
8.1.16, the password is sent in UPPERCASE.
If you send a command from an 8.1.6 Server, the password is send a
Dear Team
We have upgraded tsm server to v8.1.16 and all our automation scripts start to
fail due to invalid password thorough correct password is provided.
If you update sessionsecurity=transition then if we try same credential then it
works but command routing will not work.
If you update
