AAC vs. Authenticated DFC

I've read about the Application Access Control (AAC) tokens and the Authenticated DFC instances. What (if any) is the difference in use?

It appears that the AAC tokens expire, so it appears to be less of a permanent solution than an Authenticated DFC.

We are looking at securing access to our Content Server so that only a given Webtop application and a couple other non-Documentum applications can query the CS and its content. Does it matter which solution we use? Or for that matter, is there a practical difference between the two approaches?

Thanks in advance for the responses.

Find more posts tagged with

Comments

DCTM_Guru

I suggest you look at privileged client feature. This will guarantee that only apps from certain IP address can connect to your repository.

matsuzak

Thanks for the response Johnny. So is the privileged client as easy as it seems in DA?

And this is just for the machine level, correct? It does not specify an application running on the machine?

DCTM_Guru

I believe its both application and machine. I do remember seeing entries for same machine when I had multiple web apps deployed to single app server.