There is a vulnerability in IBM WebSphere Application Server that could allow an HTTP response splitting attack in Channel.
More information on this link
Author: <span>kenio.carvalho</span>
- <WAS_INSTALL_DIR>/bin/> wsadmin -conntype NONE
- wsadmin> securityoff
- wsadmin> exit
- Restart the servers.
- Enable the security from administrative console.
- Once the needed corrections are made, you can re-enable security in the admin console and then restart WebSphere.
Several versions of WebSphere Portar are vulnerable.
BM WebSphere Portal could allow a remote attacker to obtain sensitive information, caused by the failure to restrict access to resources located within web applications. An attacker could exploit this vulnerability to obtain configuration data and other sensitive information.
How to fix this vulnerability ? Go to this link from IBM
I setup my IBM Connecitons integration with Sametime Proxy 9. The Connections server SSL is made using a self certificate.
I used this tool when i was migrating from V8.0 to V8.5.5. This guide is a must read for WPS Administrators.
This guide provides a comprehensive approach to performing staging to production using Portal Application Archive (PAA) in IBM WebSphere Portal 8.5.
Introduction
Preparing the source environment
Preparing the target environment
Creating the initial release
Deploying the initial release
Updates with syndication
Updates with ReleaseBuilder
Known Problems
Acknowledgments
References
Change History
click here to read the full article
I setup the integration between Sametime Proxy 9.0 and IBM Connections a long time ago.
When i access the Connections homepage the sametime widget does not work. After some research i found a solution.
I need to install the Sametime Server Proxy Certificate on my browsers. After that the Sametime integration works fine on Firefox, Chrome, Safari and IE.
For a long time i used Domino Blog template, since version 7.0.2. I moved the blog to WordPress this weekend.
The migration process was not so beautifull. I just read the blog posts using a feed reader and then import into WordPress.
I had some problems, related to WordPress security plugin, but now almost everything is ok.
Today a customer ask why his IBM Connections is not sending notifications and recent upddates is not working anymore.
I got the SystemOut.log and see the following:
| [10/1/15 11:20:15:201 BRT] 000001e2 JMSPublisher E com.ibm.lconn.events.internal.publish.impl.JMSPublisher publishEvent CLFWY0148E: Could not obtain an event connection [10/1/15 11:20:15:201 BRT] 000001e2 LocalExceptio E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method “publishEvent” on bean “BeanId(Communities#lc.events.publish.jar#EventPublisher, null)”. Exception data: com.ibm.lconn.events.internal.invoke.async.AsyncEventInvokerException: CLFWY0148E: Could not obtain an event connection at com.ibm.lconn.events.internal.publish.impl.JMSPublisher.publishEvent(JMSPublisher.java:200) at com.ibm.lconn.events.internal.publish.impl.JMSPublisher.publishEvent(JMSPublisher.java:164) |
The problem: The message engine was not working (started).
To solve the problem:
1 – Shutdown the Connections nodes
2- Clear some files on the disk
(Delete only the files but not the directories)
Restart the servers
IBM’s internal testing on iOS 9.x devices has shown that the iOS 9.x native Calendar app may remove some repeating Domino calendar entries from the mobile device.
See this technote
From CF07, you can manually syndicate by using the following methods:
Update
- This method syndicates items that are newer than the previous syndication. Items that are newer than the last syndication on the syndicator are sent to the subscriber. Items that are newer on the subscriber are not updated. Items that are created on the subscriber that do not exist on the syndicator are not removed from the subscriber.
Rebuild
This method syndicates all items that are newer on the syndicator. All items that are newer on the syndicator are sent to the subscriber. Items that are newer on the subscriber are not updated. Items that are created on the subscriber that do not exist on the syndicator are not removed from the subscriber.
Rebuild with mirror
If you select the mirror option, all items on the subscriber are reset to mirror the syndicator. All items that are newer on the syndicator are sent to the subscriber. Items that are newer on the subscriber are overwritten with the older version from the syndicator. Items that are created on the subscriber that do not exist on the syndicator are removed from the subscriber. Version history is not syndicated.