Popular Tags

  • Quick to-do for updating Docker web with commercial certifications - Cook Book

    Easy to remember, it can already be read in many places the creation of a csr for the creation of the commercial cert for a wildcard openssl req -new -nodes -keyout my.key -out my.csr -newkey rsa:xxxx Generating a RSA private key ....................…

  • GW24.1 -Certificates what did the developpers smoke

    i.e. GWIA would not do SSL, with the groupwise created certificates just for fun I created my onwn certificate following https://portal.microfocus.com/s/article/KM000006608?language=en_US replace the groupwise created, same path, same name and gwia…

  • GW24.1 -Certificates what did the developpers smoke

    i.e. GWIA would not do SSL, with the groupwise created certificates just for fun I created my onwn certificate following https://portal.microfocus.com/s/article/KM000006608?language=en_US replace the groupwise created, same path, same name and gwia…

  • Change S/MIME user cert for proxy

    Hello, an assistant is supposed to send encrypted emails from a proxy account. Since she has her own certificate installed and set as default, she can't do that unless she sets the cert of the proxy account as default, at least thats what I have seen…

  • GroupWise Admin console, and click on the Messenger object, I get a PKIX certificate error

    With GroupWise 18.4.2, the error that appears in the Admin console is: Error communicating with resource (https://<messenger_fqdn>:8315/hosts?Preload=100&Limit=5000&IDsOnly=true): javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun…

  • Groupwise gwcalsvr keystore error

    Using GWise 18.4.2 Server with multiple IPs GWise MTA/POA run on one IP GWCALSVR run on another IP We use commercial wildcard certificates after upgrade gwcalsvr does not start In the /var/log/novell/groupwise/calsvr/calsvr.log we see…

  • Commercial certificates for GWWEB not working but have problems now

    Was very happy yesterday that my docker GWWEB installation worked fine from the beginning. SSL SOAP connection to PO worked fine too. Today I relaced the server.crt(.key) with a symlink "ln -s <path to FQDN hostname.key server,key" same for the crt…

  • D103 - Post office not found

    In preparation for 18.4, in my test environment running 18.3.1, I've gone ahead and updated my certs as per KM000004502 so they all have the proper fqdn name , and recreated the certs. I have one server in this environment hosting 3 POAs. I updated…

  • Gw18.4 upgrade certificate questions

    I've read what's been posted here in the forums and support article KM000004502, but I'm still hesitant to begin to attempt the upgrade of 18.4 because of all the certificate requirements and having it blowing up on me :) Bear with me, it's alot of…

  • Primary domain moved - How to update Messenger, Calpub and Mobility?

    Hello We have moved our Primary and Secondary domains to a new server with new IP/new DNS. All remote groupwise servers have had the new certs updated as well as their respective POA/MTA/GWIA certs. The only thing I'm uncertain is how to bring these updates…

  • Domain not Trusted Redux

    Why, oh why... Does it seem like every time a new version of GW comes out, I spend countless hours trying to break into the admin console because the CA cert gets hosed? I am beyond tired of having to chase my tail trying to install the CA cert into my…

  • Devices can no longer connect

    Running Data Synchronizer 1.2.4 (was 1.2, but I've upgraded it as part of the troubleshooting process) on SLES 11.1. At some point on November 30th user devices could no longer connect, previous to this the system has been stable. The Web UI looks completely…

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.