Lapas

Friday 4 December 2015

About Domino Designer Workpace restore


Source: http://www.intec.co.uk/restoring-domino-designer-including-working-sets/
Another one: http://www.lotusguru.com/lotusguru/LGBlog.nsf/d6plinks/20100310-83ESQC

Quote:

Since 8.5.0 I’ve been searching for everything that needs to be done to restore Domino Designer. Some time ago I blogged about exporting and importing Domino Designer preferences but I had always struggled to work out which files / folders were required for Working Sets.
Today I decided to do a clean install and finally managed to track down all the relevant folders to have working sets installed in a few seconds. All are in the workspace folder
  • workspace stores all the relevant folders for servers and applications you’ve accessed
  • workspace.metadata.plugins/org.eclipse.ui.workbench has settings for various dialogs, plus the critical file workingsets.xml. This looks like it has the configuration for the working sets themselves and points to paths of relevant files. I copied the whole folder.
  • workspace.metadata.plugins/org.eclipse.core.resources has the projects referenced in the workingsets.xml. The whole folder is required. The .location files in each project point to the location using a URI relative to JNSF, which I suspect is the workspace folder
  • workspace.metadata.plugins/com.ibm.designer.domino.ide.resources has a file that maps the projects to the actual servers
Copy those into a clean install, and you have “working” working sets in a few seconds.
I then chose to manually install all the additional plugins, but those appear to be in workspace.configorg.eclipse.update. To get the list of locations I had previously used in Domino Designer, I just copied a backup of bookmark.xml into that folder.

Monday 29 June 2015

Domino Client Certificate authentication (web services consumer/provider)

Short description of problem and requirements:
Required to provide SSL Client authentication for IBM/LOTUS Domino users and other remote systems.
Integrate web services without storing username/password for Web Service connections consumers/providers or providing anonymous access.

Problem resolution example:
1) In Domino server document for SSL authentication options must set Client Certificate to "Yes".
How domino recognizes connecting client with certificate. It searches address book for matching user/server with corresponding mapped certificate.
Web Service provider - uses standard authentication - user must send client certificate to server. If this type of authentication is enabled, then there should be no problem.
Web Service consumer - using IBM Notes consumer we should set SSL option for connection, that Client Certificate must be sent and for this purpose additional option must be set before connecting  Setssloptions(NOTES_SSL_SEND_CLIENT_CERT).

Where are the benefits?
You can build SOA based applications and integrate Lotus Applications with Web Services, so it could be later exposed to other applications.

Possible scenario:
1) Create Web service, that approves some document.
It could be used by:
a) Notes client - create internet certificate for user and import in notes ID. Approved document from LN Client.
b) Same Domino server with Client certificate authentication enabled (no username/password required). Server side scripts.
c) Web browser client - if server uses username/password authentication - user already authorized for operation.
d) External applications - create new user in address book, create client certificate, integrate.