- HCL Connections Newsletter v2 and Join Community requests
- Show Community Create Button only to users with role "community-creator"
- Makefile to process all Asciidoctor files in a directory
- Update on the Touchpoint workaround
- Linkdump Week 44 / 2020
- Linkdump Week 42 / 2020
- Linkdump Week 41 / 2020
- Elasticsearch index creation problem
- Linkdump Week 40 / 2020
- Selfhost Shaarli
Last week I had an issue that some Domino Server didn’t provide SSO through SPNEGO any longer (environment worked for over 2 years now). This environment uses the customized domcfg.nsf template of Andreas Artner, maybe it’s related, but I don’t think so, on Windows 7 with latest Internet Explorer 11 and Domino Servers 9.0.1 with latest fix pack. So what happened? The Domino servers are placed in the “Local Intranet Zone” of IE through Group Policy from beginning. The Windows administrators started to enable “Enterprise Mode” for better handling of compatibility mode and one of the steps is to deactivate the “Display intranet sites in compatibility View” option.
Some more points to my working configuration of Single Sign-On in Lotus Notes. Automating configuration with plugin_customization.ini I do a lot of software tests with my productive Notes Client (on Mac OS), so i often delete the Expeditor-folder in ~/Library/Application Support/Lotus Notes Data/. So i place configuration details in /Applications/Notes.app/Contents/MacOS/rcp/plugin_customization.ini, then the settings get automatically applied. # Connections Config com.ibm.lconn.client.base/server=http\://connections.example.com/profiles com.ibm.lconn.client.base/authtype=DOMINO-SSO com.ibm.lconn.client.base/dominosso.dominoresolveservername=false com.ibm.lconn.client.base/authserver=$hierarchical Domino-Server-Name$ com.ibm.lconn.client.base/dominosso.useclustermates=true com.ibm.lconn.client.base/dominosso.preferred.username.field=ShortName com.ibm.lconn.client.base/policy-mode=OVERWRITE com.ibm.lconn.client.base/enableConnectionsIntegration=true # Sametime Config com.ibm.collaboration.realtime.community/name=$Name for Community$ com.ibm.collaboration.realtime.community/host=$Hostname of Sametime Server$ com.ibm.collaboration.realtime.community/defaultAuthType=ST-DOMINO-SSO com.ibm.collaboration.realtime.community/authServerUrl=$hierarchical Domino Server Name$ com.ibm.collaboration.realtime.community/loginByToken=true com.ibm.collaboration.realtime.community/tokenLoginOnly=true com.ibm.collaboration.realtime.community/loginAtStartup=true com.ibm.collaboration.realtime.login/autologin=true com.ibm.collaboration.realtime.login/alwaysLoggedIn=true com.ibm.collaboration.realtime.imhub/disableExit=false # Status Updater Fix to show profile pictures com.ibm.lconn.statusupdates/download.image.enabled=true Sametime will only apply the settings of plugin_customization.
In only two weeks starts LCTY Edcom Nachlese 2012 in Munich. I prepare a session on Single Sign On in Notes / Domino environments. So i had time to check some settings in Lotus Notes. Since 8.5.3 we have a new option Domino-SSO for Connections Plugin. I made several tests with my installed Notes Client on Mac OS, but i had no success. I tested with several settings in the preferences dialog and with different settings in plugin_customization.ini. I had one configuration where i can use Sametime Tokenbased Login and leave “Domino Single Sign-On Server” empty in connections preferences, but this works only with running Notes Client and i had to apply the setting again after restart the client.