Use the Get-CsAuthConfig cmdlet to retrieve the authentication configuration for your organization.

Use the Get-CsAuthConfig cmdlet to retrieve the authentication configuration for your organization.

This cmdlet gets authentication configuration from two server roles - Registrar and WebServices.

It is meant to only be run at the global level.

If you do run it at the pool level and only one of the roles are present on the pool, the cmdlet will return the setting that corresponds to the role that exists on the pool and the global settings for the role that doesn’t exist on the pool.

If neither role is present on the pool, it will return an error.

If both roles are present for the pool, but policies are not defined at the pool level, the cmdlet will return an error.

Use the Set-CsAuthConfig cmdlet to modify the authentication configuration for your organization.

Use the Set-CsAuthConfig cmdlet to modify the authentication configuration for your organization.

There are 5 different configurations that are supported as you can see in the parameters section.

This cmdlet sets configuration on both the Registrar and the Web Services roles.

It is only meant to be run at the global level (and not at the pool level), and we highly recommend that you only use it in this manner.

However, technically it can be run at a pool level.

But realize that if the pool only has one of the roles needed (say, Registrar and not Web Services), then only the settings for Registrar will be set and the Web Services settings will come from the global setting.

No special warning will be given because some settings were not set.

If a client uses the Registrar settings from one pool and the Web Services settings from another pool and the authentication settings are in an inconsistent state, the client may be unable to log on.

If neither role is present for a pool, both Get will return an error message.

If both roles are present for a pool but policies aren't defined at the pool level, Get will return an error message.