When you run a Service from the Authoring Environment, Teamworks launches a new browser window.  The Authoring Environment needs to authenticate to the Server so it passes your username and password in plain text in the url.  The Server then redirects to a page that does not display your credentials. 

Without going into esoteric reason about why passing passwords around in plain text is bad, I have a simple example.

We were running through some test scenarios in a room full of users and decided to launch a test services from the A.E.  Up popped the web browser window with my username name and password in full view for the entire room to see and then the server froze.  After 10 seconds or so, something woke up and the page finally redirected.

One of the users was kind enough to point out to the entire room that my password was displayed in the address bar.

Just peachy…

I suspect there are ways around it but none of them are terribly convenient.