In our trial Nomad installation we have two users (both administrators) with ID files loaded into the ID Vault on the Nomad server (Domino 12.0.2FP2). I can now log in to Nomad without problem. The other user cannot. He is offered the "Please log in to Nomad" screen, and on clicking "Log In" is invited to enter his name. When he does so, and clicks "Continue", he is returned to "Please log in..."
No error message is shown. His name is typed correctly, he has a person record in the directory and an ID stored in the ID Vault.
I can see no difference in our respective configurations. What should I look for?
Hello Andrew,
You can enable the below debug on Domino server to know what it reports.
set config debug_namelookup=1
Try to login and see what it reports.
[12F4:0006-0F94] NAMELookup::<lookup> Searching view '$Users' (1 of 1 views), flags = 0x0.
[12F4:0006-0F94] NAMELookup::<lookup> Searching name='Peter Meter' (1 of 1 names).
[12F4:0006-0F94] NAMELookup::<lookup> Searching DBIndex=1.
[12F4:0006-0F94] NAMELookup::<LocateNameSpace> locate namespace in DBIndex=1, view='$Users'
[12F4:0006-0F94] NAMELookup::<ReturnNameInfo> name='Peter Meter' was found '0' match(es)
[12F4:0006-0F94] NAMELookup::<lookup> No matches found for name 'Peter Meter' in dbIndex '1'
[12F4:0006-0F94] NAMELookup::<lookup> NumReturned=0, TotalNumReturned=0 match(es) for name='Peter Meter'
If it shows in the server console as above. Then you might try editing the re-saving the person document helps.
Steps:
1) Edit the person document and make any dummy entry in the Work/Home tab.
2) Issue the below command on the server.
load updall -t ($Users) names.nsf -R
3) Now try accessing the Nomad and see how it go.
Thank you
Regards
Shrikant J
Thank you, @Shrikant Jamkhandi . Does the verbose logging get stored anywhere, or is only ephemeral on the console?
Hi Andrew, the traces are seen on the live Domino console and also recorded in the console.log file of the Domino server which is under data\IBM_Technical_Support folder.
Thank you
Regards
Shrikant J
Thank you!
But while that database exists (neither it nor the folder are shown in the "Open" dialog, but can be typed) the server will not share it.
Although I am opening it through the Domino server, it is as if I am trying to access it locally.
You should probably open a formal support case so we can see the full logs on both the client and server sides.
In the browser, it is a good idea to also check the call to https://mynomadserver.com/nomad/userConfig.json to ensure the JSON has a valid (non-empty and correct) userCN and homeServerCN.
Hi Robert. Isn't that .json file only for when you want to configure something non-standard?
As it turns out, the user in question (a fellow administrator) can now log on to Nomad. Nothing has changed that we are aware of.
userConfig.json is used for initial setup ("standard", not "non-standard") but then also as the heartbeat to know if the server is reachable or not (controlling the "Online"/"Offline" status in the lower right).
For the setup part, one off setup issues like you describe have often been due to the userConfig.json content being incorrect, so that is why I said to check it out.
I don't have an explanation as to why it would now be working if you didn't change anything, but the fact that it is working is at least a good thing.