Community Component

26.3.0

New Features

• You can now use a user name and password to authenticate against OTDS repositories. Previously, the Password parameter that you pass to the UserRead or Security action when authenticating against an OTDS security repository had to be an already-obtained JWT (JSON web token). Now, Community accepts the user password, in the same way as for other security libraries.

• For the OTDS repository, you can now configure Community to accept user names from a list of OTDS fields. You can set the new OTDSUserField parameter to a list of field names, which can include user attributes. When you use a JWT (JSON web token) to authenticate, Community authenticates the user if the supplied user name matches a value from any of the configured fields in the tokeninfo response that OTDS returns.

• You can now configure Community to automatically create a set of users when it starts.

  You can configure the new [AutoCreateUsers] configuration section with a numbered list of sections, each of which contains details on a user to create. Each section must contain a Username and InitialPassword parameter to set the user name and password for the new user. It can optionally also include an EmailAddress and Roles parameter to set the email address and user roles for the user. For more information, refer to the Community Help.

Resolved Issues

There were no resolved issues in this release.

26.2.0

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

26.1.0

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

25.4.0

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

25.3.0

New Features

• In the OpenText Directory Services (OTDS) security library, you can now configure Community to access an OTDS REST API endpoint at a URL nested below the server root, for example when you access it through a reverse proxy that adds a path prefix. To add a path prefix, set the OTDSPath in the security repository configuration section.

• You can now control resource ID requirements for authentication against an OTDS repository, by using the RequireResourceID parameter in the security repository configuration section. By default, you must set the ResourceID parameter on the Security or UserRead action. You can alternatively set RequireResourceID to the ID of a resource that you want to require for all users, in which case Community ignores the ResourceID action parameter. You can also turn off resource ID checking entirely by setting RequireResourceID to False, in which case no specific resource access rights are required to authenticate the user.

Resolved Issues

There were no resolved issues in this release.

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.