We have just moved to a new web server. The old server ran Domino 5.0.5; the new one runs 7.0.1. I have a database that I’ve been working on that uses a readers field to control web access. On the old server, user jjones logged in via a browser and was presented with a list of 3 documents based on the readers field. I replicated the database to the new server, and the user login works just the same as on the old server, the header comes up just as it did on the old server, but user jjones does not see the 3 documents.
Is there something different between the two Domino versions that could affect this?
Subject: Readers not working on web after move to new server
Eric,
I would troubleshoot as if this were any old reader names problem, and not specifically look to the Domino version. For example:
Same domain, or is domain different between servers?
If you make a bogus form with a field that returns @UserName, is the user Jim Jones? Or CN=Jim Jones/O=Acme?
If flat, then is the user’s hierarchical name the same as the server’s hierarchy? It must be so. If the user’s name is canonical, then it’s ok for that hierarchy to be different than the server’s.
Also, verify that the docs are really there, that it isn’t simply that this server’s name wasn’t included in the reader names list and therefore the server never got those docs replicated in the first place (for example).
Subject: RE: Readers not working on web after move to new server
Raphael,The servers are in the same domain. The users are authenticated via a special address book for this purpose. I did some experimenting using your suggestion #2, and found that depending how I had jjones set up in the address book, @Username would either tell me that I was logged in as jjones or as CN=jjones/O=Mayfield (which would be the same as the server’s hierarchy). I put both jjones and CN=jjones/O=Mayfield in the readers field of one of the documents, but still I saw no documents.
Subject: RE: Readers not working on web after move to new server
Eric,
A few thoughts:
So if you look at these docs via your super id in the notes client, and do doc properties at the view level, you see that the data type and everything is correct for the ReaderNames field, right? It’s SUMMARY and READ-WRITE?
If Yes to #1, then the user should be able to access the document, so don’t use the view or agent or whatever they’re using, but just make a new view for this test. Have the view explicitly reference these docs by whatever fields make sense, just to keep the view small and fast for your test. Confirm with notes client that the doc appears here. Now have the user login and see if they see it. If so, then the problem might just be the code being used to render the docs to them, not the docs themselves. In other words, the embedded view they’re using on serverB isn’t including the docs, or whatever.
I know that the way you set the user up in the address book affects how they really login, but my point is that once they’re logged in, they either need to be fully canonical or else flat with same hierarchy as the server. Often, when people move from serverA to serverB, they find that the servers might not share a hierarchy (/Lotus becomes /IBM, for example). A good way to verify this is with a bogus form that just has a field with @UserName in it so that you can verify how your user is being perceived by the server.
Subject: RE: Readers not working on web after move to new server
Raphael,The readers field is correct–the data type says SUMMARY READ-ACCESS NAMES.
There are no real users of this database (yet), just myself and the bogus user jjones. There are only 5 documents, so there’s no danger of a view being too large.
Unlike jjones, I have access to the documents based on being a member of a group, and I can see all 5 documents when using the Notes client. I created a test form on the web with a field displaying @UserNamesList. When logged in via a browser, all of my groups were correctly displayed, including the one that gives me access to the documents. I then changed the web launch of the database back to the view in which I should see the documents. I figured that way I could avoid any question about hierarchy. Just for good measure, though, I put my full hierarchical name in the readers field on one of the documents. However, when logged in as myself, I saw no documents.
Subject: Readers not working on web after move to new server–Fixed
Raphael,I went into the Autoframe tab of the view I’ve been working with, removed the name of the frameset that was listed there, and now the documents display. Why that had any effect, I don’t know, but I’ll have to chalk this up as a difference between versions after all.