Hide a Security Property
Each managed security policy has security properties. Integration developers see the security properties and provide values for them while defining a connection. However, when a value is static or is programmatically derived across all connections for the adapter, you can hide the security property.
For example, consider an application that supports OAuth 2.0
Authorization Code as a security policy. Every invoke connection must use that security
policy. In such cases, you can hard code the security policy for every invoke connection
and hide the security policy. That way, you simplify the experience for integration
developers.