mfgroupwise/webacc-ng repository overview

⁠What is GroupWise Web

GroupWise Web, first introduced with the release of GroupWise 18.2, lets users access their GroupWise mailboxes through web browsers on mobile devices, tablets, and desktops.

GroupWise Web replaces GroupWise WebAccess, which is no longer being developed nor included with GroupWise.

Note: Previous versions of WebAccess still work with GroupWise 18.3.2 and later.

This image is the tech preview of GroupWise Web 26.2.0.

If you want to participate in our technical preview to see what is coming in GroupWise Web, go to https://hub.docker.com/r/mfgroupwise/webacc-ng⁠ and register for the tech preview.

https://www.microfocus.com/en-us/products/groupwise/overview⁠

⁠Registering for the Forum

To provide feedback during the technical preview, you need to do so on the tech preview workspace (https://vibe.microfocus.com/novl/workspace/groupwise_web_tech_preview⁠). You will need to be registered for the workspace before you can add any feedback. Follow the steps below to register for the workspace:

1. Create a microfocus.com/novell.com account if you do not already have one: https://login.microfocus.com/nidp/app/login?id=115&sid=0&option=credential&sid=0⁠

2. Using your microfocus.com account, login to the tech preview workspace: https://vibe.microfocus.com/novl/workspace/groupwise_web_tech_preview⁠

   When you enter your credentials, you will get an Access Denied message, but your account is created in the Vibe system so you can request rights to the workspace.

3. Email your microfocus.com/novell.com username and email address to [email protected] with the subject of Registration saying you have established an account on the tech preview workspace and that you would like to participate in the tech preview.

4. You will receive a response when you have been granted rights to the tech preview workspace. It will include directions on how to access the workspace to ask questions and provide feedback. The workspace includes feedback forums and helpful information on using GroupWise Web.

⁠Using This Image

Prerequisites and instructions for using this image are included under the release features. For information, see How to Use This Image⁠.

⁠Feature Releases

• May 7, 2026 - 26.2.0 Release⁠
• December 9, 2025 - 25.4.0 Release⁠
• June 27, 2025 - 25.2.0 Release⁠
• November 18, 2024 - 24.4.0 Release⁠
• July 17, 2024 - 24.3.0 Release⁠
• April 10, 2024 - 24.2.0 Release⁠

For information about GroupWise Web 18.5 and earlier releases, see GroupWise 18 Release Notes⁠ or contact OpenText Support⁠.

⁠May 7, 2026 - 26.2.0 Release

This release includes the following:

• Custom column configuration popup in the Preview Pane: You can now right-click in the preview pane header to have a pop up window appear that allows you to change the column headers by adding, removing, and reordering the headers.
• Multi-Factor Authentication (MFA) bypass: Administrators can now configure Multi-Factor Authentication (MFA) bypass which allows LDAP users to be exempted from MFA requirements when accessing GroupWise Web from the internal network. They are still required to use MFA when connecting externally.
• GW Web Calendars can now be published.

⁠December 9, 2025 - 25.4.0 Release

This release includes the following:

• Folders now show the number of unread emails next to each folder. You can filter by unread messages in the folder. The unread filter is also available in advanced search.

• Tech updates:

  • Updated to Angular 20.

  • Migrated from TinyMCE to Froala Editor.

⁠Known Issues

• When sending an email to an external email address, the message displays unwanted borders/box outlines around in the content. This is fixed in Tech Preview build 148624.

⁠June 27, 2025 - 25.2.0 Release

This release includes the following:

• OpenText Access Manager integration for Single Sign-On.

• KeyShield SSO integration.

• Global Search enhancements including filters.

⁠OpenText Access Manager Integration

In order to configure OpenText Access Manager in GroupWise Admin Console, the following must be known/obtained from the NAM Administrator:

• DNS host name or IP address for the NAM server

• Connection port to the NAM server

• (Optional) SSL certificate for the NAM connection, if using SSL

• NAM Client ID

• NAM Client secret

In the GroupWise Administration Console, you enable NAM and enter this information by navigating to System > GroupWise Web > NAM Authentication. The NAM integration can be enabled/disabled at a user, post office, or domain level in the Client Options. In the event that the connection with NAM is lost after enabling the integration, users will still be able to login to GroupWise Web as long as Allow fallback to GroupWise Authentication is enabled in the Client options.

Important: By default, SSL is enabled for NAM when running the Docker image. If SSL needs to be disabled for NAM, update the Docker run command by adding NAM_SSL_VERIFY=off.

Important: Advanced Authentication (AA) with NAM is not yet tested. Please do not try to use both AA and NAM.

⁠KeyShield SSO Integration

With KeyShield SSO configured for GroupWise Web in GroupWise Administration, users that are authenticated in the KeyShield Desktop Client with the KeyShield Plugin installed in their browser will be automatically logged into GroupWise Web when it is launched. KeyShield SSO login is also supported for proxy login in GroupWise Web.

For information about configuring KeyShield in GroupWise Administration, see https://www.novell.com/documentation/groupwise24/gw_guide_admin/data/b1f0s9ux.html⁠ and https://portal.microfocus.com/s/article/KM000040266?language=en_US⁠. No additional configuration is required for GroupWise Web.

Important: Do not use both NAM and KeyShield SSO at the same time. Use only one or the other.

⁠November 18, 2024 - 24.4.0 Release

This release enhances the implement of the GroupWise Web integration with OpenText Secure Messaging Gateway (SMG). This release adds the following:

• Scan messages before they are sent.
• Scan signatures before creating or modifying them.
• Indicator on attachments (light green for successful or light red for failed) to show if it passed the SMG scan.

We have also enhances the security of GroupWise Web by changing the variant of nginx that we use to nginx:alpine. Because of this change, if you need to make changes to the running image container, you need to run the following command: docker exec -it /bin/sh.

⁠July 17, 2024 - 24.3.0 Release

This release includes the initial implementation of GroupWise Web integration with OpenText Secure Messaging Gateway (SMG). With SMG configured in GroupWise Administration, SMG executes security scans of composed messages in GroupWise Web. Mail items that fail a scan will not be sent. GroupWise Web users are notified when Mail items fail a scan. This gives them an opportunity to fix the security issue and try resending the item.

In order to configure SMG in GroupWise Administration, the following information must be known/obtained from the SMG Administrator:

• DNS Host name or IP address for the Secure Gateway server

• Connection port to the SMG server

• SMG application key

• Access to the SMG CA certificate, if using SSL

In the GroupWise Administration Console, you enable SMG and enter this information by navigating to System > GroupWise Web > Secure Messaging Gateway. In the event that the connection with SMG is lost after enabling the integration, users will still be able to send GroupWise Mail items without scanning. However, by default, attachments to mail items will not be included. You can override this behavior and allow attachments if you select the last setting in the Secure Messaging Gateway configuration, "Process attachments if scanning is interrupted." In either scenario, users are prompted with the appropriate information when SMG scanning is offline. More information about configuring SMG in GroupWise Administration Console can be found in Configuring Secure Messaging Gateway⁠.

Once you have configured SMG in GroupWise Administration, you need to incorporate the SMG host into your docker run command. Use the following switch to add it to your docker run command:

--add-host=host name:IPaddress>

Example:

docker run -it -v /root/autoUpdate/gw-smg:/etc/nginx/gw --name j110-add --rm -e FQDN=webacc.acme.com -e DNS_SERVER=137.65.247.1 -p 2112:443 -e TLS REDIR=2112 --add-host=j110.qa.gwava.com:151.155.210.110 -v /root/autoUpdate:/certs img-collaboration-docker-dev.svartifactory.swinfra.net/gwbuild/webacc-ng:feature-smg

For this release, SSL is enabled for SMG when running the Docker image. If at some point you need to disable SSL for SMG, update the image using SMG_SSL_VERIFY=off in the docker run command. For reference, see Downloading and running the image⁠.

Note: For this release, you need to update the GroupWise Post Office Agent. For information on updating the Post Office, see Updating the GroupWise Post Office Agent⁠.

⁠How to use this image

• Prerequisites⁠

• Installing Docker on SLES⁠

• Downloading and running the webacc-ng-config utility⁠

• Downloading and running the image⁠

• Updating the image⁠

• Updating the GroupWise Post Office Agent⁠

⁠Prerequisites

1. Docker 19.03.5 or higher.

2. GroupWise 18.2 or later. Note: The GroupWise System version (backend) must be equal to or later than the GroupWise Web version. It cannot be an earlier version than GroupWise Web.

3. GroupWise POA with SOAP enabled. SOAP must have SSL enabled.

4. GroupWise DVA with SSL enabled.

5. (Optional) TLS certificates for GroupWise Web.

6. Fill out the GroupWise Web Worksheet⁠ with the information for your GroupWise system.

⁠Installing Docker

GroupWise Web can be run on any supported Docker platform. Use the links below to find the steps to install Docker on your desired platform:

• Docker Install documentation (https://docs.docker.com/install/overview/)⁠

• Docker Hub docker engine community downloads (https://hub.docker.com/search/?type=edition&offering=community)⁠

• Docker Engine product page (https://www.docker.com/products/container-runtime)⁠

For your convenience, the steps to install Docker on SLES 12/15 and Windows are included below:

⁠Installing Docker on SLES 12 or SLES 15

If you haven't installed Docker before, you can install Docker on SLES 12 or SLES 15 following the steps below:

1. Add the Containers Module to your server using YaST > Software > Add System Extensions or Modules. You can also add the Containers Module during the SLES install.

2. In a terminal, run the following commands:

   sudo zypper install docker
sudo systemctl enable docker
sudo systemctl start docker
sudo usermod -G docker [username] - This command lets the specified username run docker commands.

3. In a terminal, run the following command to test the docker install: docker run hello-world

For more information on Docker, see the SLES documentation below:

**SLES 12:** https://www.suse.com/documentation/sles-12/singlehtml/book_sles_docker/book_sles_docker.html⁠

**SLES 15:** https://www.suse.com/documentation/sles-15/singlehtml/book_sles_docker/book_sles_docker.html⁠

⁠Installing Docker Community on Windows

To install Docker Community on Windows, follow the steps found in Install Docker Desktop on Windows (https://docs.docker.com/docker-for-windows/install/)⁠.

⁠Downloading and running the web-config utility

1. Starting with GroupWise 18.4, the web-config utility will only run if the GroupWise Admin Service, POA, and DVA pass the new GroupWise Web Certificate Verification Process. Go to "Securing GroupWise Web using Certificate Verification"⁠ and make sure that your system complies with the information and instructions found there.

2. After ensuring that your system meets the requirements in Step 1, go to "Downloading and Running the web-config Utility"⁠ and run the web-config utility to create new configuration files that match your system.

3. Continue with the next section.

⁠Downloading and running the image

The first time you run the GroupWise Web image, you need to specify the folder that has the web.conf file and (optionally) your TLS certificates. For convenience, the Web Client can create certificates for your system. For information about certificate best practices in GroupWise, see https://www.novell.com/documentation/groupwise18/gw18_guide_admin/data/adm_secadm_cert_server.html⁠.

1. Run one of the following commands to download the desired image:

   • webacc-ng image: docker pull mfgroupwise/webacc-ng

   • multi-language build: docker pull mfgroupwise/webacc-ng-multi

2. Run the following command to run the webacc-ng image using the information from the GroupWise Web Worksheet⁠:

   docker run -d -v Web-config Location:/etc/nginx/gw --name webacc-ng --rm -e FQDN=Docker Server Name -e DNS_SERVER=**DNS Server -p 80:80 -p 443:443 -v (Optional) Server Certificate:/certs mfgroupwise/webacc-ng:latest

   • To run the multi-language build, change mfgroupwise/webacc-ng to mfgroupwise/webacc-ng-multi.

   • To run with GroupWise self-signed certificates, see the example below:

     Example: docker run -d --rm -v /opt/novell/gw:/etc/nginx/gw --name webacc-ng -e FQDN=webacc.acme.com -e DNS_SERVER=192.168.1.5 -p 80:80 -p 443:443 mfgroupwise/webacc-ng:latest

   • To run with commercially signed certificates, see the example below:

     Example: docker run -d --rm -v /opt/novell/gw:/etc/nginx/gw --name webacc-ng -e FQDN=webacc.acme.com -e DNS_SERVER=192.168.1.5 -p 80:80 -p 443:443 -v /opt/novell/gw/certs:/certs mfgroupwise/webacc-ng:latest

     Please note that /opt/novell/gw/certs should contain the server.key and server.crt files.

3. (Optional) If you want to run GroupWise Web on a different ports than 80 and 443 (this is useful if you have more than one server running in Docker), you should change the initial port number. For example, port and TLS Port: -p :80 -p :443 and add -e TLS_REDIR_PORT=port -e TLS_REDIR_PORT=TLS_port

   Example with commercial certs: docker run -d --rm -v /opt/novell/gw:/etc/nginx/gw --name webacc-ng -e FQDN=webacc.acme.com -e DNS_SERVER=192.168.1.5 -p 8080:80 -p 8443:443 -e TLS_REDIR_PORT=8080 -e TLS_REDIR_PORT=8443 -v /opt/novell/gw/certs:/certs mfgroupwise/webacc-ng:latest

You can now access GroupWise Web by going to: https://Docker_Server_Name.

Note: If you are using TLS_REDIR_PORT, you need to add the port number to access GroupWise Web.

⁠Updating the image

To update the image to the latest version, you simply need to stop the image and start up a new instance with the latest code:

1. To stop and remove the old image, run the following commands:

   docker stop webacc-ng

   docker rm webacc-ng

2. Run the following command to pull down the latest webacc-ng image: docker pull mfgroupwise/webacc-ng

3. Rerun the docker run command you used in "Downloading and running the image⁠" to use the same webacc-ng-config file and certificates.

⁠Updating the GroupWise Post Office Agent

In order to support new functionality in GroupWise Web, changes sometimes need to be made to the GroupWise Post Office Agent to which GroupWise web connects. When you need to update the GroupWise POA, a note will be added to the Available Features list. Please note that the GroupWise download (and GroupWise Web) should only be used in a test environment.

To download the GroupWise build that has the latest GroupWise Web support, go to the Tech Preview workspace⁠ and follow the links to the latest GroupWise download.

Note: To access the Tech Preview workspace and the GroupWise download, you must be registered to the tech preview forum. Follow the steps in Registering for the Forum⁠ to register.