IBM Domino 10.0.1 FP2 is available for Download

Two days ago the IBM/HCL released a new Fix Pack for IBM Domino and Notes 10.0.1, the Fix Pack 2. Take a look at the IBM Domino 10.0.1 FP2 Release Notes.

The Fix Pack is available for Download from the Fix Central:
IBM Domino 10.0.1 Fix Pack 2
IBM Notes 10.0.1 Fix Pack 2

If you are interested in running Domino on Docker, take a look at the Daniel Nashed´s Blog for the updated scripts.

Advertisements

SAML & IBM Notes Traveler – Encrypted E-Mails Issue

A while ago, we ran into issue with SAML on IBM Notes Traveler devices. The Users were not able to open encrypted E-Mails.

Before assigning Users with SAML Policy in Domino Directory, Users were able to upload their ID-File and open Encrypted E-Mails. But as soon as the SAML Policy was assigned to a user, that would not be possible anymore.

We opened a Ticket at IBM and shortly after that we got a confirmation that the issue is related to SPR # GFAL9ZBJVT . A few days ago we got a Hot Fix for this issue, which needs to be installed on the users Mail Server. After installing this fix, the users were able to open encrypted E-Mails on their Apple devices (with Companion App installed) without any issue.

The Hot Fix for SPR # GFAL9ZBJVT is not included in Domino 10.0.1 or 10.0.1 FP1 release.

Update: The Hotfix is included in Domino 10.0.1 FP1 Code, take a look at the article from Daniel Nashed.

IBM Notes/Domino G1 Language Packs Released

IBM Notes and Domino G1 Language Pack was released yesterday, part numbers are listed below.

Take note that the FP1 is not included, so you should install it right away after installing the slipstream version. And if you had the first “troubled” version of the client installed, you should uninstall the original slipstream release completely before installing the FP1 Update to ensure compatibility with FP1, as described in the official article.

IBM Notes Client 10.0.1 Multilingual User Interface

  • IBM Notes Client v10.0.1 Multilingual User Interface for Windows (Group 1) Multilingual (CC0I9ML )

IBM Notes 10.0.1 for Mac

  • IBM Notes v10.0.1 Mac 64 bit German and Italian (CC0IDML )
  • IBM Notes v10.0.1 Mac 64 bit French, Spanish, Brazilian Portuguese (CC0ICML )
  • IBM Notes v10.0.1 Mac 64 bit Korean and Japanese (CC0IBML ) – View details
  • IBM Notes v10.0.1 Mac 64 bit Simplified Chinese and Traditional Chinese (CC0IAML )
  • IBM Notes v10.0.1 Mac 64 bit French, Spanish, Brazilian Portuguese (CC0ICML )
  • IBM Notes v10.0.1 Mac 64 bit Korean and Japanese (CC0IBML ) – View details
  • IBM Notes v10.0.1 Mac 64 bit Simplified Chinese and Traditional Chinese (CC0IAML )

IBM Notes 10.0.1 for Windows

  • IBM Notes v10.0.1 Windows German (CC0HRDE )
  • IBM Notes v10.0.1 Windows Brazilian (CC0HZBP )
  • IBM Notes v10.0.1 Windows French (CC0HVFR )
  • IBM Notes v10.0.1 Windows Italian (CC0HYIT )
  • IBM Notes v10.0.1 Windows Japanese (CC0HXJA )
  • IBM Notes v10.0.1 Windows Japanese (CC0KCJA )
  • IBM Notes v10.0.1 Windows Korean (CC0HSKO )
  • IBM Notes v10.0.1 Windows Simplified Chinese (CC0HTSC )
  • IBM Notes v10.0.1 Windows Spanish (CC0HUES )
  • IBM Notes v10.0.1 Windows Traditional Chinese (CC0HWTC )

IBM Notes Designer & Admin for Windows

  • IBM Notes, Domino Designer and Admin V10.0.1 for Windows German (CC0I0DE )
  • IBM Notes, Domino Designer and Admin v10.0.1 for Windows Brazilian (CC0I8BP )
  • IBM Notes, Domino Designer and Admin v10.0.1 for Windows French (CC0I4FR )
  • IBM Notes, Domino Designer and Admin v10.0.1 for Windows Italian (CC0I7IT )
  • IBM Notes, Domino Designer and Admin v10.0.1 for Windows Japanese (CC0I6JA )
  • IBM Notes, Domino Designer and Admin v10.0.1 for Windows Japanese (CC0KDJA )
  • IBM Notes, Domino Designer and Admin V10.0.1 for Windows Korean (CC0I1KO )
  • IBM Notes, Domino Designer and Admin v10.0.1 for Windows Simplified Chinese (CC0I2SC )
  • IBM Notes, Domino Designer and Admin v10.0.1 for Windows Spanish (CC0I3ES )
  • IBM Notes, Domino Designer and Admin v10.0.1 for Windows Traditional Chinese (CC0I5TC )

IBM XWork Server

  • IBM XWork Server 10.0.1 Language Pack for Windows, AIX, Linux German (CC0IQDE )
  • IBM XWork Server 10.0.1 Language Pack for Windows, AIX, Linux French (CC0IMFR )
  • IBM XWork Server 10.0.1 Language Pack for Windows, AIX, Linux Italian (CC0IRIT )
  • IBM XWork Server 10.0.1 Language Pack for Windows, AIX, Linux Korean (CC0ISKO )
  • IBM XWork Server 10.0.1 Language Pack for Windows, AIX, Linux Simplified Chinese (CC0ITSC )
  • IBM XWork Server 10.0.1 Language Pack for Windows, AIX, Linux Spanish (CC0INES )
  • IBM XWork Server 10.0.1 Language Pack for Windows, AIX, Linux Traditional Chinese (CC0IUTC )
  • IBM XWork Server10.0.1 Language Pack for Windows, AIX, Linux Portuguese Brazilian (CC0IPBP )

IBM i

  • IBM Domino 10.0.1 Language Pack for Windows, AIX, Linux, IBM i German (CC0IYDE )
  • IBM Domino 10.0.1 Language Pack for Windows, AIX, Linux, IBM i French (CC0IVFR )
  • IBM Domino 10.0.1 Language Pack for Windows, AIX, Linux, IBM i Italian (CC0IZIT )
  • IBM Domino 10.0.1 Language Pack for Windows, AIX, Linux, IBM i Korean (CC0J0KO )
  • IBM Domino 10.0.1 Language Pack for Windows, AIX, Linux, IBM i Portuguese Brazilian (CC0IXBP )
  • IBM Domino 10.0.1 Language Pack for Windows, AIX, Linux, IBM i Simplified Chinese (CC0J1SC )
  • IBM Domino 10.0.1 Language Pack for Windows, AIX, Linux, IBM i Spanish (CC0IWES )
  • IBM Domino 10.0.1 Language Pack for Windows, AIX, Linux, IBM i Traditional Chinese (CC0J2TC )

IBM Notes Domino 10.0.1 Fix Pack 1, AppDev Pack 1.0.1 and Verse on-Premises 1.0.7 Released

IBM Notes and Domino 10.0.1 Fix Pack 1 is available for Download. There are no new Features in this release, just bug fixes, for more details take a look into the official Release Notice.

IBM Notes 10.0.1 Fix Pack 1 Download

IBM Domino 10.0.1 Fix Pack 1 Download

We also got a new Version of AppDev Pack and Verse 1.0.7 last week, take a look at the official Blog Post.

Make sure that the “Names.nsf” cannot be accessed via Internet!

Important Notice: If you are using your Domino Server as an LDAP Directory for Connections and/or Sametime do not continue with the steps described further down.


If your Domino Server is exposed to the Internet, make sure that the Domino Directory or the “Names.nsf” database cannot be accessed via Web Browser, or at least certain fields which can be used to get the hash values of the Internet Passwords.

A while ago, we got contacted by a customer who found out that his Domino Servers are vulnerable to a certain exploit which allows an attacker to extract the hash values of HTTP Passwords, of every user in the Domino Directory. The mentioned vulnerability is documented as “CVE-2005-2428”, you can read all the details of the exploit in the article bellow:

https://www.exploit-db.com/exploits/39495

EDIT: In a response to my post, Sven Hasselbach also wrote a post on his blog. It is very informative and detailed, he added Information I missed, so I would strongly urge you to read it. Furthermore the I would also like to add the comment from Christoph Stöttner:

I haven’t checked the authentication, but you can’t use LDAP any more (Softerra will present: The user has insufficient access rights!)! So even when Connections or Sametime User can authenticate (please double check), TDI will not read or update any user account, even worse with default settings in Connections TDISOL all your profiles get deactivated!

The mentioned vulnerability is from 2016! So nothing new. To get the hashes the attacker already need to have a valid login (or allowed anonymous access to your names)! Then he can grab the hashes. Afaik with “Use more secure internet passwords” and “Yes – Password verification compatible with Notes/Domino release 8.01 or greater” it’s not that easy to decrypt the hashes.

I think a way more important is proper ACL, a well-configured security tab in the server document and “Enforce server access settings: Yes” for all used protocols.

As described in the article, you could remedy this by hiding $dspHTTPPassword and HTTPPassword or, you could “block” the access to names.nsf via Web Browser completely. The only reliable way I could find, with the help of Roberto Boccadoro, to do this on Domino would be to set the following property:

I tested this in few environments, with SPNEGO and Web Federated Login enabled, and I could find no issues.

Directory Integration – IBM Domino & Microsoft Active Directory – Questionnaire

Many customers I have encountered are using tools to integrate Domino and Active Directory with each other in some form. Being that as simple as synchronizing some User Document fields using LDAP or some more problematic processes as synchronizing passwords. Some would like to have a “full” Integration with Active Directory and some would like to keep the two directories as separated as possible.

Going forward to Domino v11, IBM and HCL are thinking about a more native and subtle integration with Active Directory and the best thing about it is that everyone can express their opinion by completing the following Questionnaire:

https://epwt-www.mybluemix.net/software/support/trial/cst/forms/nomination.wss?id=5711

    So, please let the Product Management know how you feel about Directory Integration. All you need is an IBM ID, if you do not have it already, you can create one here:

https://www.ibm.com/account/reg/us-en/signup?formid=urx-19776

Domino SAML & NFL – Changing the ADFS Certificate

Recently we got contacted by a growing number of customers regarding the change of the SSL Certificate on the ADFS Server used for Domino SAML and Notes NFL. Although the process is not overly complicated, there are some “gotchas” you need to keep in mind in order for this process to go smoothly, which I will try to describe before going through the actual process of changing the certificate.

Plan ahead

Keep in mind that, as soon as you change the certificate on the ADFS Server, SAML/NFL on the Domino/Notes side will not work properly. As there is no Configuration Document in the IdP Catalog which corresponds with this certificate, thus Domino will just drop the Requests signed with the new ADFS Certificate. In this case, you will get the following errors:

SECCheckAndParseSAMLResponse> Signature verification check failed : Could not verify cryptographic signature

SECCheckAndParseSAMLResponse> Exiting : Document has been modified or corrupted since signed! (signature)

Needles to say, this will lead to the SSO Process not working and many angry users…

To remedy this, plan the certificate change so that the impact on the client machine is minimal.

For NFL to work, you need to roll-out the new ADFS Certificate (in case if you are using public CA, you need to roll out the Intermediate and the CA certificate). You would do this via Notes Client Policy, Security Settings. This is not a big deal, but keep in mind that after setting the Policy, the Users need to successfully log in, for the Notes Client to pick up the change and get the new Policy together with the new ADFS Certificate. I have seen some environments were the Notes Client needed multiple restarts to pick up the change.

Now, think about this, the certificate is expiring, and you have to change it in the middle of Christmas holidays, meaning most of the Users are on vacation, so you go ahead, do everything perfectly. But as soon as your users get back from the vacation, they try to login and they get the beautiful error message stating that NFL is not possible at this time and their Notes ID Password is requested. Resulting in Helpdesk calls… Only after they enter the ID Password and successfully login, the Client will get the new certificate and in the future the login will be possible.

In order to get around this, I would recommend rolling out the new certificate as soon as possible, before actually changing it on ADFS.

Check the Certificate Requirements

The worst scenario is using the wrong certificate, so make sure that the Certificate you are using meets the Requirements. If you are using a Self-Signed Certificate, then it must have the “keyCertSign” (also know as “Certificate Signer”) and “cRLSign” (also known as “CRL Signer”) in the “Certificate key usage” field. To check this just open the certificate and inspect that field. If the certificate does not contain these fields, than you will get the following error when you try to create a Cross Certificate from it in the Domino Directory:

“A cross certificate will not be made due to key usage restrictions in the input certificate.”

It also needs to be a “SHA2” or higher. For the full list of Certificate Requirements and more, please read the following article:

https://www-01.ibm.com/support/docview.wss?uid=ibm10718435

If you are using a certificate from the public Authority, then the purchased personal certificate will not contain these values, but this is not a problem, because you can just import the CA and all Intermediate Certificates in the Domino Directory and cross-certify them. After that you can roll-out the the Cross-Certificates via Notes Policy Document.

One customer is planning to use their own internal Windows Certificate Services or Windows PKI, I opened a Support Case regarding this, and got a confirmation that in this case you can also use the CA Certificate of that Authority. We still have not tried that and I didn´t have time to test it out in my Test Environment, but as soon as I have done so, I will post the results.

If the CA and Intermediate Certificates do not change, then you can skip the step of importing and cross-certifying these, as the mentioned certificates do not change.

Steps needed to change the ADFS Certificate

  • Check that the new Certificate meets the requirements.
  • Import the Certificate (self-signed), or CA and Intermediate Certificates if you are using a Certificate from a public Authority.
  • Cross-Certify the Certificate(s).
  • Push the newly created Cross Internet Certificates via Notes Policy (Security Settings).
  • Change the ADFS Certificate
    • As mentioned, as soon as you do this, the SAML Assertions will fail until you create a new IdP Configuration Document and restart the participating Domino Servers.
  • Export the new “FederationMetadata.xml” file from the ADFS Server.
  • Deactivate old Configuration Documents in the IdP Catalog Database.
  • Create new IdP Configuration Documents using the new “FederationMetadata.xml” file.
    • After you import the XML File, it will be deleted from the filesystem, so if you need it for another Configuration Document, make a copy of it.
  • Replicate the IdP Catalog Database if needed.
  • Restart all Domino Servers participating in SAML Authentication.
  • Delete the deactivated IdP Configuration Documents after you have made sure that the new Configuration works.