Do you want to implement Notes "public key matching" to improve security but dread the thought of how many calls you might receive because the existing user base is probably not currently well "matched?" You can use "stats and events" to determine who needs to be fixed before enabling. This will keep your help desk calls down to near zero if you perform the following tip before enabling.
In events4.nsf create a new "Events Handler"
On the "Event" tab select the following options:
- "Events can be any type"
- "Events can be any severity"
- "Events must have this text in the event message"
Enter the following (no quotes): "does not match the one used during authentication"
"Save and Close" the event handler document.
Go to statrep.nsf and open the "Events -- by Type" view. When a user connects to a server with an ID whose public key is not EXACTLY the same as what is stored in the user's Person document it will trigger an "Unknown" event which will then list in this view under the "Unknown" category.
Ask the user to send you their public key and update their Person document with it. Continue monitoring and fixing for a few weeks until you feel comfortable that all or most mismatches have been fixed and THEN enable "Exact Key Match" with no pain.
Do you have comments on this tip? Let us know.
This tip was submitted to the SearchDomino.com tip exchange by member Tom Panucci. Please let others know how useful it is via the rating scale below. Do you have a useful Notes/Domino tip or code to share? Submit it to our monthly tip contest and you could win a prize and a spot in our Hall of Fame.
