cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
666
Views
0
Helpful
6
Replies

PE Authentication Problem

Justin Ferello
Level 5
Level 5

All,

We upgraded to 14.1.1 recently from 14.1 and ever since then PE fails to authenticate to TMS from the VCS, we get this for each of the services:

ServiceUsers
StatusFailed
ResponseHTTP exception
Reason(400) HTTP Error : WWW-Authenticate
Last updated
Last polled2013-01-09 11:50:42
Next scheduled poll2013-01-09 11:52:42
Cluster peer performing the pollingThis VCS

I have verfied the username & password about 25 times now.  I can open any browser and navigate to the TMS server via HTTPS and using the same username & password I connect fine.

TMSProvisioning Diags show green for everything.  Firewall on TMS server is off.  Just using the local Windows admin account on the TMS server for all authentication purposes, so I know there is nothing weird.

Thanks,
Justin

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ
6 Replies 6

Magnus Ohm
Cisco Employee
Cisco Employee

Hi Justin

Jens Didriksen had a simlar issue. Search for the error in this forum, there is a workaround for it.

/Magnus

Sent from Cisco Technical Support iPhone App

Magnus,

Thanks for the information, I did review Jen's case and this is what his solution was:

"Uninstalled TMSPE

Uninstaled TMS

Rebooted server

Uninstalled NET framework 4

Uninstalled IIS

Rebooted server

Downloaded and re-installed NET framework 4

Rebooted server

Re-installed TMS 13.2.1 and allowed it to configure IIS

Re-installed TMSPE

Rebooted server"

That is crazy, I am pratically rebuilding the server for an authentication issue?

I will run the Wireshark and I guess open a TAC case since this seems like it is going to be a huge thing.

Thanks,

Justin

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ

Magnus Ohm
Cisco Employee
Cisco Employee

Can you do a wireshark trace on the tms server and change the protocol to http. Just verify the exception code. I have seen 400 in tms when the shark trace shows 401 which is much easier to solve. If you cant get around it i would suggest a tac case.

/Magnus

Sent from Cisco Technical Support iPhone App

Magnus Ohm
Cisco Employee
Cisco Employee

I know we have discussed it internally. Hopefully there will be a better solution for this soon!

/Magnus

Sent from Cisco Technical Support iPhone App

Justin Ferello
Level 5
Level 5

Magnus,

I got it working, thank you for your time though.  I enabled 'Basic Authentication' on the /tms & /tmsagent virtual directories in IIS.  Interesting note though, in your Hardening guide for TMS is states to uncheck everything but Integrated Auth, but your normal TMS admin guide says it must be integrated & basic

I assume having basic auth enabled on the /tmsagent was actually the one that did it though, right?

Thanks,

Justin

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ

Magnus Ohm
Cisco Employee
Cisco Employee

It can be several factors causing that error. I have tried that in another case where it was unsuccessful. But glad it was simple for you this time :).

/Magnus

Sent from Cisco Technical Support iPhone App