Centralized Configuration for WSA with Authentication Realm

[Garry Cross]

Hi I cannot find clarification with regard to the above topic.

We have 8 WSA in various cities across the country. Each have a realm configured with the same name. All are using the same configuration otherwise. Each locations Realm is slightly different in terms of the AD server they are configured with. Each has 3 targets the first of which is the local Domain Controller, then one in another city and finally the one in the data center.

What I don't understand is the comments in the user guide about using different authentication realms. Since the realm itself is local to the WSA and can't be configured on the SMA it is my expectation that the Realm itself is not centrally managed and not pushed to the individual WSA's. The only thing that would be an issue if different Realm names were in use the the policies configured. Is this a correct statement?

We are getting ready to do centralized config and would like to know other's experiences in this regard.

Thanks in advance.

[Johnatan Dire]

i have this problems too. can you help me?

[sadik.sener1 · Accepted solution]

Hi,

If you are using the same realm name it should not prevent you from using SMA.

Sma is using the configurations under the Web Security menu.  

There, you have your identification profile. Your identification profile knows which realm it will consume to get identity information.

As long as the realm name matches, it will not consider which servers does that realm connect. (To get user ip mappings.)

SMA should not change the configurations of Realm even if you want it to do.

Sadik