Showing results for 
Search instead for 
Did you mean: 
Walkthrough Wednesdays

configuring TSP username through registry

This document was generated from CDN thread

Created by: Stephan Steiner on 01-03-2010 07:58:38 AM
One of our customers recently asked that. They used to be on CCM4 and as part of the login script, they configured the TSP through the registry so that the appropritate username (they use ccm login = domain login) is written to the appropriate registry key.
They've been upgraded to CCM6.1 and now that mechanism doesn't work anymore. I did have a look at how TSP stores the configuration in release 6, and as far as I can tell, it stores its configuration in HKLM/Software/Cisco Systems, Inc./Cisco TSP/Cisco TSP001. In there there's a string (REG_SZ) key called UserName which looks promising - however, it seems it only contains the first character of whatever username I enter in the TSP configuration. And if I go the other way round and write something in the registry, what I get in the TSP configuration is all garbled up.
I've compared the before and after state of the entire TSP Registry key but cannot find any keys changing but UserName when I change the username so I'm left wondering where the rest of the username has gone.

Subject: RE: configuring TSP username through registry
Replied by: David Staudt on 01-03-2010 07:43:34 PM
The registry entry for UCM 5+ is in unicode - vs. ASCII for CM4 - so I'm sure what you're seeing is the script/app writing ASCII usernames into what should be a unicode field.  Hopefully this is easy for them to fix. 
Note, it is not possible to provision the TSP password field, as it has to be encrypted by the TSP config pages runtime - the encryption algorithm is not published.

Subject: RE: configuring TSP username through registry
Replied by: Stephan Steiner on 02-03-2010 08:26:06 AM
David - I suppose it shouldn't be a problem to do string encoding in javascript/vbscript. However, what bothers me is that I only see one character in the UserName field.. regardless of character encoding, it should be longer, right? With unicode we'd even have two bytes per character.. so while it wouldn't be directly redable, we should see a longer string, right?

Subject: RE: configuring TSP username through registry
Replied by: David Staudt on 02-03-2010 02:39:18 PM
Right click the userName field in Regedit and try 'Modify Binary Data' should be able to see the encoded data.

Subject: RE: configuring TSP username through registry
Replied by: FRANK JONG on 03-03-2010 12:28:20 PM
The registry does not support unicode as is.
Because the username characters consist of two bytes, you will probably only see the first char, because the first (multibyte)char is like 0x00AB in bytes it would read 0xAB 0x00 where 0x00 is the end of the string.
So it's probably correct to see only 1 char
Content for Community-Ad