Skip to main content
D
davehaigh13-Aquamarine
13-Aquamarine
March 23, 2015
Question

auth.properties & Trusted hosts in 10.2

  • March 23, 2015
  • 4 replies
  • 2240 views
Trusted Host Setup

4 replies

D
davehaigh13-AquamarineAuthor
13-Aquamarine
March 23, 2015
Ok, I found a partial answer on the PTC Community Site.

David Haigh
T
TomU23-Emerald IV
23-Emerald IV
March 24, 2015
I haven't verified that using the hostname actually works, but the property WILL let me enter it:
xconfmanager -s wt.auth.trustedHosts=Host1 -t codebase/wt.properties -p

To enter more than one host, put the entire statement in double quotes:
xconfmanager -s "wt.auth.trustedHosts=Host1 Host2" -t codebase/wt.properties -p
(or)
xconfmanager -s "wt.auth.trustedHosts=xxx.xxx.xxx.xx yyy.yyy.yyy.yy" -t codebase/wt.properties -p

As far as auth.properties, I have that in the root Windchill folder (WT Home). The only line inside it is "auth=$user" (without the quotes).

The location of the file is set in the wvs.properties file (<wt home=">\codebase\WEB-INF\conf\wvs.properties)
publish.cadconvert.PROE=com.ptc.wvs.server.publish.CadConvertPROE,useworkerdownload\=$(wt.home)$(wvs.dir.sep)auth.properties

Tom U.
J
jessh12-Amethyst
12-Amethyst
March 24, 2015
It's easier in cases like this to edit site.xconf yourself in my opinion.

If you do it via the command line then you need to follow appropriate
quoting practices for the platform in question to ensure that what you
want treated as one argument actually is, e.g.:

xconfmanager -s "wt.auth.trustedHosts=xxx.xxx.xxx.xx xxx.xxx.xxx.yy"
-t codebase/wt.properties -p

Also be really careful about copy/pasting to/from any Microsoft
product. These products like to turn "-" into "–", which is a
completely different character that command-line programs will not
accept as an equivalent of "-".

D
davehaigh13-AquamarineAuthor
13-Aquamarine
March 24, 2015
So then let me point out that CS182327 is incomplete. It says"
Provide multiple value with whitespace delimited.
* e.g. wt.auth.trustedHosts= <host_ip> <host2> <host3>

No double quotes shown.

When I document things, I include double quotes where ever they may be needed, even if for that specific instance I could do without them.
It eliminates a lot of confusion.

For example, in the line below, I don't really need double quotes around the yellow paths, but I do around the green path. Keeping them consistent even if it not needed is the better way to document this.
echo y|copy "P:\configs\core-config.txt"+"P:\configs\dted-config.txt"+"P:\configs\core-mapkeys.txt" "C:\ptc\Creo 2.0\Common Files\%CREOVERSION%\text\config.pro"

David Haigh
Terms & ConditionsAccessibility statement