Community Component

Community Component is an ACI server. For details of changes that affect all ACI servers, see ACI Server Framework.

25.2.0

New Features

  • Community can now read an AES key for security info encryption directly from a configuration setting. You can now set the SecurityInfoKeys configuration parameter to a verbatim AES key. Previously, it was only possible to set a list of TEA encryption keys, or the path of an AES key file on disk.

    This feature enables you to import a key directly from a secret source, such as an environment variable or HashiCorp® Vault. The key protects user security info tokens, which in turn allow access to secure documents, so OpenText recommends that you do not supply it as a plain text configuration value. Setting a plain text value returns a configuration validation error, but does not prevent the server from starting up.

Resolved Issues

There were no resolved issues in this release.

25.1.0

There were no new features or resolved issues in this release.

24.4.0

There were no new features or resolved issues in this release.

24.3.0

There were no new features or resolved issues in this release.

24.2.0

New Features

  • You can now use Community to authenticate with OpenText Directory Services (OTDS). In particular, it can verify a login token and the user name present in that token. You configure the OTDS library (uas_otdssecurity.dll) as a security repository in the same way as other repositories. To connect to the OTDS server, set OTDSHost and OTDSPort, and SSLConfigOTDS if required. For example

    [OTDS] 
    library=uas_otdssecurity
    OTDSHost=<IP address>
    OTDSPort=8443
    EnableLogging=TRUE
    SSLConfigOTDS=SSLSettings
    
    [SSLConfig]
    SSLMethod=Negotiate

    You can then send user actions with the DeferLogin parameter set to True, setting UserName to the OTDS user name, Password to the token for that user, and ResourceID to the resource that you specified as the scope when you request the token.

    action=UserRead&repository=OTDS&username=<username>&password=<token>&resourceid=<resourceid>&deferlogin=true

    For more information, refer to the IDOL Community Component Help.

Resolved Issues

There were no resolved issues in this release.

24.1.0

There were no new features or resolved issues in this release.

23.4.0

New Features

  • For NT security, you can now configure Community to accept user login details that contain any valid UTF-8 character, by setting the new UseUTF8 parameter to True. You set this parameter any configuration section where you define settings for a user_ntsecurity library, for example [NT].

Resolved Issues

There were no resolved issues in this release.

23.3.0

There were no new features or resolved issues in this release.

23.2.0

There were no new features or resolved issues in this release.