Query results for : March 2015
Remove Welcome pages with Greasemonkey- 27 March 2015 - (0) Comments
Thomas Hampel
27 March 2015If you are like me trying to delete all cookies and all cached elements with every browser restart, annoying banners or welcome pages like this one will show up every time you log in.
I am taking eBay as an example here but of course the same concept applies to other sites.
Firefox users can use a small Greasemonkey script to change this once and forall.
all you need to know is what element from the page you need to hide, Firebug is your friend here.
Highlight and click the elment you are interested in and Firebug wll open the respective line of code.
So we now know that the div id pt-tray_0 and/or all elements with class "pt-tray" is what we are looking for.
With some little jQuery the CSS properties of the element can be changed to display style none which will hide the element.
$(".pt-tray").css("display","none")
To make a permanent solution lets wrap it into a Greasemonkey script:
Now just install the latest version of Greasemonkey, restart Firefox and go to Tools\Greasemonkey\Manage User Scripts.
Click New User Script....
define a title and name space.... and add use this small piece of code
// ==UserScript==
// @name eBay NoBanner
// @namespace com.thomashampel.ebay.NoBanner
// @include http://www.ebay.de/*
// @version 1.0
// @grant none
// ==/UserScript==
hideBanner();
window.setTimeout(hideBanner,500);
document.addEventListener("load",hideBanner,true);
function hideBanner(){
$(".pt-tray").css("display","none")
}
// @name eBay NoBanner
// @namespace com.thomashampel.ebay.NoBanner
// @include http://www.ebay.de/*
// @version 1.0
// @grant none
// ==/UserScript==
hideBanner();
window.setTimeout(hideBanner,500);
document.addEventListener("load",hideBanner,true);
function hideBanner(){
$(".pt-tray").css("display","none")
}
Once saved, restart Firefox again to see the result:
Result:
PANIC Unexpected internal error returned to logger 0x20692010- 27 March 2015 - (0) Comments
Thomas Hampel
27 March 2015Tip of the day:
When running Domino server commands on the operating system of a server, make sure to run the command from a console with Admin access rights, otherwise you'll get this:
PANIC: Unexpected internal error returned to logger: 0x20692010
Reference:
SPR # PALL8WA3Y8
Solution
Open a command prompt by right clicking and selecting "Run as Administrator", then run the command(s) again.
Root cause:
Problem in front of keyboard.
Sametime Missing single sign on token - again- 23 March 2015 - (3) Comments
Thomas Hampel
23 March 2015Once again a customer ran into an issue with Missing Single Sign On Token - I have blogged about it before
The Problem:
Initial authentication is working fine, but when disconnecting the network cable + reconnecting again, users see "Missing SingleSignOn Token", or authentication does not work at all without any error message.
The problem can be resolved by restarting the client. However, this is not an acceptable solution.
Analysis
As mentioned earlier, authentication via Domino SingleSignOn is working fine at the first Notes Client logon On the client, the configuration pretty much looks like that:
I've enable the following debug parameters as described here in the file rcpinstall.properties which is located in the folder
com.ibm.rcp.accounts.level=FINEST
org.apache.commons.httpclient.level=FINE
com.ibm.workplace.internal.notes.security.auth.level=FINEST
com.lotus.sametime.community.level=FINEST
com.ibm.collaboration.realtime.community.level=FINEST
com.ibm.collaboration.realtime.im.community.level=FINEST
com.ibm.collaboration.realtime.login.level=FINEST
com.ibm.rcp.internal.security.auth.module.level=FINEST
com.ibm.rcp.internal.security.level=FINEST
com.ibm.rcp.security.level=FINEST
org.apache.commons.httpclient.level=FINE
com.ibm.workplace.internal.notes.security.auth.level=FINEST
com.lotus.sametime.community.level=FINEST
com.ibm.collaboration.realtime.community.level=FINEST
com.ibm.collaboration.realtime.im.community.level=FINEST
com.ibm.collaboration.realtime.login.level=FINEST
com.ibm.rcp.internal.security.auth.module.level=FINEST
com.ibm.rcp.internal.security.level=FINEST
com.ibm.rcp.security.level=FINEST
Restarted the Notes client and started testing to reproduce the problem. Looking at the error log
Within the error log file of the client which is located in
Further down in the log there is even more information about this exception.
Solution
It seems like the LtpaToken requires an hierarchical name of a server in order to be validated correctly. This can be done either by specifying the hierarchical name in the field "Host server" of your connection preferences, but doing so willl show an alert that you should use a fully qualified DNS name in this field.
So better put the hierarchical name in the Authentication server field as shown here:
This can be any server which shares the same LtpaToken with the Sametime server, of course you can also specifiy the Domino name of the Sametime server here.
How to deploy this setting automatically?
Within the managed community settings the parameter "authServerUrl" is used for this setting.
You can use a Desktop Policy setting to push this configuration setting down to all your clients. In the Managed Settings section, just add the following:
Item : authServerUrl
Value : hierarchical name of your Domino server, e.g. DominoServer/OU/Org
Plug-in name : com.ibm.collaboration.realtime.community
And you're done :)
Remarks
- A complete list of settings that can be predefined within the Sametime client by using Domino policies is available here
- Technote 1320442 - Collecting data for Embedded Sametime client for Notes 8.x clients
- Technote 1391284 - Pushing policy settings to the client for updating notes.ini and Eclipse preference settings
