Notes Shared Login/Notes Federated Login and Smart Card Support

One of our customers wants to implement Single-Sign-On for Notes Clients on Windows Operating Systems and in the future they plan to implement Smart Cards as a Login mechanism on Windows PCs.

Due to some misleading official articles, I was not sure if Smart Cards are supported with NSL or NFL. After a check with IBM Support, it turns out that Smart Cards are supported with Notes Shared Login and Notes Federated Login, as long as you do not use “Smart Card Protected ID” Feature.

So, as long you use Smart Cards solely for OS access/login you are good to go to use NSL or NFL for Notes SSO.

Advertisements

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.

Engage 2019 – Part Two – Notes 11, Future of Connections and more!

After the exciting first two days, we continued at the same pace, the first sessions started at 8 o´clock. So after grabbing a few cafe cups and making some hard decisions on which Sessions to visit, I started going toward the presentation rooms. Just like in the previous post, I will list the Sessions I have visited and add some Information, which from my perspective is most important.

IBM Engagement Center Quickstart: Get your first Intranet pages up and running in minutes – by Martti Garden

In this Session, Martti unleashed the full power of ICEC and showed some tips and tricks, like resizing YouTube videos automatically, in order to “rock” any Connections Environment.

Notes 11 – by Ram Krishnamurthy

This got pretty interesting, by the way, as you can imagine, the room was completely full. Ram presented us the new Notes 11 Client. The Session consisted from three parts, first we got to see what HCL is striving to Achieve with the new release. We basically got a glimpse of how it should look at the end.

After that, we got to see the current state of the pre Beta release.

After the Design was presented, Ram explained us some technical differences and improvements which are going to be available on the new Notes 11 client.


IBM Connections: The Future is Bright – by Danielle Baptiste and Martti Garden

In this Session Danielle confirmed that HCL is going to continue to invest into Connections Platform, because of a strategic importance for HCL. Martti also showed us some new features which are going to come with the new CR Releases, like Integration with Slack! We also got to see what is coming with Connections 6.0 CR5, which is going to be released in the next two weeks. After the CR5, we should get at least two more CR Updates this year.

Domino on Docker Bootcamp – by Daniel Nashed and Thomas Hampel

Interested in running Domino (including Traveler) on Docker!? If that´s the case, then this was the session to be. Daniel and Thomas explained everything you need to know to “kick-start” your Domino deployment on Docker.

Domino and SSO – New Ways for secure collaboration – Round Table by Daniele Vistalli

In this Round Table Daniele presented his own Application/Solution for generating SSO Tokens, meant for environments or Use Cases where you can’t use SAML. The application is great, it is based on Domino and it shows just how versatile the platform is.

IBM Connections Customizer – Have it Your Way! – by Miki Banatwala

Miki showed us the true power and flexibility of IBM Connections Customizer. What I liked the most was the possibility to show different content based on different user groups.

Sadly could not visit all Sessions, every track had at least two or three sessions which were interesting to me, so it was always a tough call which session to choose.
Like always, the organization of the Conference was brilliant, many thanks to Theo!

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.

IBM Application Access – Support on Windows Terminal Servers

Every now and then we have a customer who would like to use  the IBM/HCL Notes or ICAA Client on Windows Terminal Servers, but this is officially not supported. Since a few days there is an Idea on “Domino Product Ideas” forum regarding this.

So if you are a customer or another Business Partner who would benefit from the Support of IBM Application Access on Windows Terminal Servers, please vote for the following Idea:

https://domino.ideas.aha.io/ideas/NTS-I-489