Security Configuration Parameters
The [Security]
section lists your security repositories, specifies generic settings for them, and contains a subsection for each of the listed security repositories. Within each subsection, specify the parameters to apply to the security repository.
NOTE: In a unified configuration, you must specify these parameters in the [UserSecurity]
section.
-
The Community component ignores security types that do not have a matching configuration section.
-
If you rename a security type, Community treats it as a new security type.
-
Removing a security type leaves the corresponding user security fields intact.
-
Community returns details of the configured security responses in the response to the GetStatus action. It also logs a
successfully loaded
message for every library it loads. -
If Community cannot load a security repository library, it logs an error message and shuts down.
NOTE: If the configured library does not exist, Community does not shut down. You can check that all your security libraries are configured correctly by checking the GetStatus response.
For example:
[Security] DefaultSecurityType=0 DocumentSecurity=True SyncRolesFromGroups=False SecurityUsernameDefaultToLoginUsername=False 0=Autonomy 1=NT 2=Notes [Autonomy] Library=C:\OpenText\KnowledgeDiscovery\modules\user_autnsecurity EnableLogging=False DocumentSecurity=False SecurityFieldCSVs=none [NT] CaseSensitiveUserNames=False CaseSensitiveGroupNames=False Library=C:\OpenText\KnowledgeDiscovery\modules\user_ntsecurity EnableLogging=False DocumentSecurity=True V4=True SecurityFieldCSVs=username,domain Domain=DOMAIN DocumentSecurityType=NT_V4 [Notes] Library=C:\OpenText\KnowledgeDiscovery\modules\user_notessecurity EnableLogging=FALSE NotesAuthURL=http://notesserver/names.nsf DocumentSecurity=TRUE CaseSensitiveUserNames=FALSE CaseSensitiveGroupNames=FALSE SecurityFieldCSVs=username DocumentSecurityType=Notes_V4