|Latest 7 Posts
| Update to RHEL 7.4 breaks DB2 Cluster (TSAMP / RSCT)|
Tue, Nov 28th 2017 12
| Domino 10 – to be continued!|
Mon, Nov 6th 2017 8
| IBM Connections 6 – Following and Followers blank|
Wed, Oct 25th 2017 6
| Exchange integration into WebSphere Portal (SSO – Kerberos)|
Tue, Sep 26th 2017 9
| User provisioning for IBM Connections Cloud – You have the choice|
Mon, Aug 28th 2017 4
| SAML & IBM Connections 5.5 – not a dream team|
Fri, Aug 18th 2017 6
| IBM Docs – Migration from DB2 –> ORACLE|
Fri, Jul 7th 2017 7
| Configuration of secret key storage in WebSphere Application Server|
Thu, Mar 12th 2015 20
| DB2 Instance autostart does not work on SLES 12 / RHEL 7|
Tue, Jul 12th 2016 20
| WebSphere custom TAI – Doing SSO the right way|
Tue, Sep 6th 2016 19
| SAML – Enterprise SSO in the WebSphere world|
Mon, Jul 20th 2015 14
| Update to RHEL 7.4 breaks DB2 Cluster (TSAMP / RSCT)|
Tue, Nov 28th 2017 12
| How To: Set AD Password using java – IC5.5 self service|
Thu, May 12th 2016 11
| WebSphere Portal – Change WCM AD Group permissions using memberFixer|
Fri, Apr 8th 2016 10
| Security Bulletin: Vulnerabilities in Apache Struts affects IBM WebSphere Application Server (CVE-2016-1181 and CVE-2016-1182) (2016.06.28)|
Tue, Sep 13th 2016 10
| IBM Connections Docs – file preview not possible for some CCM pdf files|
Thu, Nov 17th 2016 10
| HTTP Outbound authentication via SAML|
Tue, Oct 6th 2015 9
||IBM Connections (SDI aka TDI) – Synchronize users based on group membership
IBM Connections (SDI aka TDI) – Synchronize users based on group membership
The standard assemblyline „sync_all_dns“ synchronizes user data from a LDAP source into IBM Connections profiles database. As selection criteria, which users get synchronized / on boarded to IBM Connections an LDAP-filter is used (a standardized search expression with special LDAP-syntax).
But in some customer projects there are more complex requirements than just using a LDAP-filter. Many customers want to synchronize users based on a LDAP group membership. You might say… „No problem, that´s easy“ Yes it is for Active directory, because each user entry has the „memberOf“ attribute for each group it belongs to so that you can easily use this to filter which group the user belongs to.
But many of our customer environments use DOMINO or SDS (aka. TDS) where you cannot make use of such a “memberOf” attribute. SDS provides the “ibm-allGroups” attribute that also returns the groups the user belongs to but this is a list of groups that you cannot create a simple LDAP filter for. My colleague Konstantin did a great job in extending the standard assembly line so that only users from a specific group get synchronized.
For this case IBM provides a mechanism to use an own iterator or lookup connector (it replaces the components that sync_all_dns uses – all the rest is standard sync_all_dns assembly line). Here you can find a description, how this can be setup
In our specific case, we only need to customize the iterator connector. This assembly line iterates over all LDAP users that should be synchronized to IBM Connections. When you use the standard “sync_all_dns” AL, the assemblyline _internal_ldap_iterate does this job… So that we’ll use this one as base for our custom iterator:
Simply copy the _internal_ldap_iterate and rename it to _custom_ldap_group_iterate:
You can also rename the LDAP iterator to „ldap_groups_iterate“. Then change the connection properties. We’ll use own properties for Group „Search Base“ and Group „Search Filter“and add those properties to the file “profiles_tdi.properties”:
The „ldap_group_iterator“ connector delivers all group members together with all attributes. Nested groups are automatically resolved. Some internal attributes such as „ibm-entryUuid“ (we`re using SDS here) cannot be resolved using this method. But we need to have this attribute so that „sync_all_dns“ can synchronize this user (GUID is used here as hash value between database and LDAP). For this an additional LDAP-lookup is needed (this lookup uses the standard properties that come from the profiles-tdi.properties file):
As „Link-criteria“ we use the „dn“ of the user.
Next step is to save and publish the assembly line (save it as groupsIterateAdapter.xml) in the packages folder of our tdisol directory.
Then you have to make changes to the “profiles_tdi.properties” file:
here you specify, that sync_all_dns should use our custom “_custom_ldap_group_iterate” assembly line as repository iterator.
We add three new properties to the file “profiles_tdi.properties”:
#The base where you want to search for groups
#Filter for the groups
After this you need to run the script „fixup_tdi_adapters.sh“ to bind these properties to all assembly lines in the packages folder.
You can now start „sync_all_dns“ and you will only synchronize users that are part of the given (or nested) groups. Cool stuff
Btw. inactivation / deletion also works using this AL. In my opinion this is a far better way than letting the customer create flags in LDAP for users that should be on-boarded to IBM Connections
Feb 03, 2015
| Recent Blog Posts
Update to RHEL 7.4 breaks DB2 Cluster (TSAMP / RSCT)|
Tue, Nov 28th 2017 9:33a GIS Techblog
Update to RHEL 7.4 breaks DB2 Cluster (TSAMP / RSCT)
after updating a RHEL 7.3 system to RHEL 7.4 the DB2 HADR / TSAMP cluster stopped working. I was able to establish the HADR connection but the service IPs were not assigned to the network interface.
Executing the command “lssam” to display the cluster state showed that nearly all resources are in the “Pending online state”.
First of all I though it is an issue with the cluster config – so that I deleted th
Domino 10 – to be continued!|
Mon, Nov 6th 2017 8:48a GIS Techblog
Welcome to the first post about IBM Domino on our GIS AG Techblog!
Here at GIS AG, we have a dedicated IBM Domino team made up of certified specialists for everything from development, to administration, support and beyond. On this blog we will be sharing the latest news and technical information about IBM Domino.
If you have any questions or comments, please, feel free to write an Email to: email@example.com
Visit our About Us page!
Domino 10 – This year Notes and Domino 9.0
IBM Connections 6 – Following and Followers blank|
Wed, Oct 25th 2017 8:42a GIS Techblog
IBM Connections 6 – Following and Followers blank
during the last weeks we had to deal with a strange problem in an IBM Connections 6 environment.
The system was migrated from IC 5.5 to IC 6 and live for about 4 weeks when suddenly the following problem occurred:
Neither users that I follow nor followers were shown in the UI. Despite installing the latest Fixes no bigger changes have been performed on the system.
I was able to follow a user:
Then opening “Following
Exchange integration into WebSphere Portal (SSO – Kerberos)|
Tue, Sep 26th 2017 12:03p GIS Techblog
Exchange integration into WebSphere Portal (SSO – Kerberos)
During the last years working with Portal I had several challenges with WebSphere Portals HTTP Outbound Proxy (aka. Ajax Proxy) in terms of authenticating backend calls to various other systems.
What we`ve done so far in terms of SSO / backend authentication:
– Authenticating using LTPAToken
– Authenticating using SAML
– Authenticating using SPNEGO / Kerberos (this was a new one for me)
The challenge this time
User provisioning for IBM Connections Cloud – You have the choice|
Mon, Aug 28th 2017 1:42p GIS Techblog
User provisioning for IBM Connections Cloud – You have the choice
Customers who use IBM Cloud for Connections, Sametime or other applications face the problem to manage their cloud accounts. For some single users you can use the Web frontend to add or change user accounts or to assign subscriptions and licenses to users. But in real world scenarios it is not possible to manage thousands of users manually or to keep them synchronized with an on-prem user repository or LDAP.
This can be handled
SAML & IBM Connections 5.5 – not a dream team|
Fri, Aug 18th 2017 7:45a GIS Techblog
last week we had to fight with an activation of SAML on a IC 5.5 CR3 environment.
The setup was:
IBM Connections 5.5 CR3 as test instance
ADFS Server 3.0 (I know… it is only tested with ADFS 2.0 – but works with 3.0 too)
We followed the instructions from the IBM Connections Knowledge Center. Smooth setup everything standard procedure. When testing this setup, the redirect to the IdP was initiated. After logging into the IdP the browser was redirected to IBM Connections ACS
IBM Docs – Migration from DB2 –> ORACLE|
Fri, Jul 7th 2017 9:52a GIS Techblog
IBM Docs – Migration from DB2 –> ORACLE
within our last big project, we had the challenge to transfer the IBM Docs database from DB2 to ORACLE. Within this database comments and other document related data is stored.
Officially there is no script available to perform this move using DBT (remove constraints / transfer / reapply constraints). We looked into the database and figured out how to perform this task using DBT – so we are not dependent on any other products. We m
IBM Connections – trouble adding additional nodes|
Wed, May 31st 2017 2:52p GIS Techblog
IBM Connections – trouble adding additional nodes
we are currently involved in a project where we installed a 1 node IBM Connections 6 Cluster and later added a second node to the cell.
So far so good… Everything that needs to be done after adding the second node is described here … Everything? Yes, mainly… but not in the mandatory details as I think! Missing custom properties and other settings might result in non-functional nodes. Especially not setting httpSess
SNOUG 2017 Presentation – SikaConnect goes External|
Thu, Mar 23rd 2017 1:06p GIS Techblog
SNOUG 2017 Presentation – SikaConnect goes External
yesterday I was at SNouG in Zurich. I had a great time there – good speakers and a overall perfectly organized event (would we expect sth. else from Switzerland? )
Raymond Weber from SIKA Informationssysteme AG and I did a session about the SIKA Extranet Feature:
Whiteboard in IBM Sametime Meeting 9.0.1 removed|
Fri, Mar 17th 2017 10:43a GIS Techblog
Whiteboard in IBM Sametime Meeting 9.0.1 removed
IBM implemented in Sametime Meeting 9.0.1 a whiteboard function as technical preview. Ben described in his articel how to enable this feature:
With the current cumulative Fix 901-ST-General-FP-SMOL-AK4G43 for the Meeting Server IBM has removed this function.
The response on my PMR was:
“I can confirm The Meetings Whiteboard feature release is being put on hold indefinitely.