Lotus Notes Driver: Trouble Creating a User Without a user.id File

Absent Member.
Absent Member.
0 0 10.4K
0 Likes

Question:


When trying to have the NotesDriverShim register a Lotus Notes user (create a new Notes user) without creating a user ID file we insert a 'no-id-file="true"' XML attribute into the add element. When the command is submitted to the NotesDriverShim to add the user, the following error occurs: "4299 - Required registration argument not provided".


What can be done to avoid this error?



Answer:


Prior to Lotus Notes / Domino 6.5, this error was not a issue. See this cool solution tip for more info: http://www.novell.com/coolsolutions/tip/18774.html.



Domino 6.5 added Certificate Authority features, which caused the registration process to be more 'refined'. As such, to create a new user without a user.id file, the Notes Driver custom parameters must be set with an intimate understanding of their underlying effects. In other words, you have to spend hours of trial and error with your driver policies, or be an IDM Lotus Notes Driver Wizard to figure this out by simply reading the documentation.



The error mentioned in the question above is caused by the driver policy requesting that Lotus Notes register a new user without creating a new user.id file (no-id-file="true"). The Notes registration process is intricately intertwined with .id files, and setting everything 'exactly right' with respect to the Lotus Notes programming API is neither easy, nor well documented. To cause the error to go away, you will need to create a user.id file for the new user by setting the 'no-id-file="false"' custom parameter (and then delete the file later...not what you really want to do) or to add a "certifier-name" custom parameter (XML attribute) on the add operation. However, if you choose this latter option, then you will also need to use a 'use-certificate-authority="false"' parameter if you are not using a certificate authority (CA) to register the new user..
Thus, to work-around the present problem, try applying the following add element attributes via policy:




  1. use-certificate-authority="false"

  2. certifier-name="OU=myOrg/O=org"

    where "OU=myOrg/O=org" represents the containment (certificate name) of the certifier ID specified to register the user.



To provide some background to this problem, here are a few references to similar problems mentioned on the public Notes Domino forum:




The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.