<p>The catalog mode specifies how to expose layers and resources in the catalog that a user does not have privileges or via anonymous access.</p><p><strong>HIDE</strong> is the default mode and hides layers that the user does not have read access for. This is the most secure catalog mode. In the event the user has read but not write permissions this mode forces the layer to be read only. This mode excludes layers from the capabilities document that the user does not have read permissions for. Because of this this mode does not work very well with clients such as uDig or Google Earth, where authentication occurs only if the server returns a HTTP 401 after an attempt to access a secured layer.</p><p><strong>MIXED</strong> mode hides all layers the user does not have read permission for but triggers authentication for any other attempt to access the layer or its metadata directly. This mode is useful in cases where a layer is not to be advertised in a capabilities document, but select access to the layer may be granted to users (DataSecurityPage authentication) who are given direct access to the layer.</p><p><strong>CHALLENGE</strong> mode allows free access to layer metadata, but issues a 401 code triggering authentication for any attempt to access the layer data. This mode lists all layers in a service capabilities document and allows operations that return only metadata such as GetFeatureInfo and DescribeFeatureType without authentication. Any operation like GetMap or GetFeature that require actual data access result in a 401 code triggering authentication. This mode works well with capabilities driven clients such as uDig.</p>
<p>The catalog mode specifies how to expose layers and resources in the catalog that a user does not have privileges or via anonymous access.</p> <p><strong>HIDE</strong> is the default mode and hides layers that the user does not have read access for. This is the most secure catalog mode. In the event the user has read but not write permissions this mode forces the layer to be read only. This mode excludes layers from the capabilities document that the user does not have read permissions for. Because of this this mode does not work very well with clients such as uDig or Google Earth, where authentication occurs only if the server returns a HTTP 401 after an attempt to access a secured layer.</p> <p><strong>MIXED</strong> mode hides all layers the user does not have read permission for but triggers authentication for any other attempt to access the layer or its metadata directly. This mode is useful in cases where a layer is not to be advertised in a capabilities document, but select access to the layer may be granted to users (DataSecurityPage authentication) who are given direct access to the layer.</p> <p><strong>CHALLENGE</strong> mode allows free access to layer metadata, but issues a 401 code triggering authentication for any attempt to access the layer data. This mode lists all layers in a service capabilities document and allows operations that return only metadata such as GetFeatureInfo and DescribeFeatureType without authentication. Any operation like GetMap or GetFeature that require actual data access result in a 401 code triggering authentication. This mode works well with capabilities driven clients such as uDig.</p>
None
that a user does not have privileges or via anonymous access.</p>
<p><strong>HIDE</strong> is the default mode and hides layers that the user does not have read
access for. This is the most secure catalog mode. In the event the user has read but not write permissions this mode forces the layer to be read only. This
mode excludes layers from the capabilities document that the user does not have read permissions for. Because of this
this mode does not work very well with clients such as uDig or Google Earth, where authentication occurs only if the
server returns a HTTP 401 after an attempt to access a secured layer.</p>
<p><strong>MIXED</strong> mode hides all layers the user does not have read permission for but
triggers authentication for any other attempt to access the layer or its metadata directly. This mode is useful in cases
where a layer is not to be advertised in a capabilities document, but select access to the layer may be granted to users
(DataSecurityPage authentication) who are given direct access to the layer.</p>
<p><strong>CHALLENGE</strong> mode allows free access to layer metadata, but issues a 401
code triggering authentication for any attempt to access the layer data. This mode lists all layers in a service
capabilities document and allows operations that return only metadata such as GetFeatureInfo and DescribeFeatureType
without authentication. Any operation like GetMap or GetFeature that require actual data access result in a 401 code
triggering authentication. This mode works well with capabilities driven clients such as uDig.</p>