Default ECL settings
When you first edit the ECL, it includes the following signatures and access options. By default, the ECL does not allow access to protected operations for active content that is unsigned, or for active content that is signed by a signer who is not listed in the ECL.
Signature |
Applies to |
Default access options |
---|---|---|
-Default- |
Formulas and code that contain a signature that is verified by Domino®, but that does not match any entry in the ECL. For example, if the
signer is Dan Misawa/Renovations, but the ECL does not contain this
signature, then the ECL uses the |
None |
-No Signature- |
Formulas and code that contain an invalid or corrupted signature, are unsigned, or are signed by an identity or organization that cannot be verified by Domino®. For example, if the code is
not signed, or is signed by a user unknown to the Domino® server, the ECL matches |
None |
BT Mail and Calendar Migration Tools/Lotus Notes® Companion Products |
Every template related to Binary Tree Mail and Calendar Migration Tools. If your organization is not using this tool, you can remove this entry from the ECL. |
|
Domino® Unified Communications Services/Lotus Notes® Companion Products |
Every template related to Domino® Unified Communications Services. If your organization isn't using this tool, you can remove this entry from the ECL. |
|
Lotus® Fax Development/Lotus Notes® Companion Products |
Every template related to Lotus® Fax for Domino®. If your organization isn't using this tool, you can remove this entry from the ECL. |
|
Lotus Notes® Template Development / Lotus Notes® |
Every template shipped with Domino® and Notes®. For example, the signer matches this type only if it has the Lotus Notes® Template Development/Lotus Notes® signature. |
All |
Sametime® Development/Lotus Notes® Companion Products |
Every template related to IBM® Sametime®. If your organization isn't using this tool, you can remove this entry from the ECL. |
All except Access to workstation security ECL |
You can also add additional users or signature types to the ECL. You could add the hierarchical names of specific users or groups -- for example, Dan Misawa/Sales/East/Renovations. If you create a special certifier to certify the IDs of a group of trusted signers, you could use a wildcard character to name all signers -- for example, */Trusted Signers/Renovations.
The following table describes the access that these users (or signature types) in an ECL would have:
Signature |
Applies to |
---|---|
*/Trusted Signers/Renovations |
Formulas and code that have */Trusted Signers/Renovations signature. For example, if the signer is anyname/Trusted Signers/Renovations -- such as Andy Brunner/Trusted Signers/Renovations or Dan Misawa/Sales/East/Trusted Signers/Renovations -- the ECL uses the */Trusted Signers/Renovations signature to match access. |
Dan Misawa/Sales/East/Renovations |
Formulas and code that have Dan Misawa/Sales/East/Renovations as the signature. For example, the signer matches this type only if the ECL contains the Dan Misawa/Sales/East/Renovations signature. |