Middleware Server

This second approach starts with the base assumption that the core identity information is stored somew other than on the AAA server. AAA clients access this identity store directly when applicable and interfac the AAA server when some interpretation or action on this data is necessary. For example, if the user re in the NOS (which is fairly common), clients can access the data directly over the protocols native to the the same repository can be used by dial-up users when translating through the AAA server. This topoloc in Figure 9-2.

Figure 9-2. Middleware AAA Topology

Roûl Ubfr j RepCiWy 5 [H05 or Olher DC)

Roûl Ubfr j RepCiWy 5 [H05 or Olher DC)

[View full size image] AAA

Figure 9-2. Middleware AAA Topology

[View full size image] AAA

ArirUVniStratve AutfwnticaiiOfi

NOS Sacurty User QiawJp

ArirUVniStratve AutfwnticaiiOfi

Clieni

This option is more likely than the root AAA server but is still hard to implement because of integration i between the applications, AAA server, and user repository. Both the middleware deployment and the ro> deployment appear identical to the user because, in both cases, there is a single user store.

100 SEO Tips

100 SEO Tips

100 SEO Tips EVERY SEO Enthusiast Should Know. This Report 100 SEO Tips will help you to Utilize These Tips to Dominate The Search Engine Today.

Get My Free Ebook


Post a comment