COMMAND

    Lotus Notes

SYSTEMS AFFECTED

    Lotus notes R4.5.3b to R5.0.2b (migration)

PROBLEM

    Puah Chun Han  and his team  found following.   On R4.5.3b server,
    some databases are having their default access set to "No Access".
    Which means  on the  Web browser  if the  link is  click, a  popup
    screen will  appear prompting  user to  enter ID  & passwords  for
    authenthications.

    This  is  what  happen,  we  upgrade  to  R5.0.2b  using  standard
    installations for a application  server, then after which  we load
    HTTP services as usual.  However with the same access control  for
    default user with "NO Access", this time when we click the link on
    the browser.   It gives  a error  " Error  403/404 -  You are  not
    autorised to perform  this operation" and  the popup login  screen
    did not appear at all.

SOLUTION

    It  was  later  found  out  that  one  could solve this problem by
    simply editing & saving nothing to the Lotus Notes address  books.
    This is   at the  "Server Configurations"  document, click  on the
    "Edit" button &  then click on  "Save & Close"  without making any
    changes  to  the  documents,  then  force  a  replications  to the
    newly migrated  application server.   After replication,  issue  a
    command "Tell HTTP  Restart" to restart  the web services.   After
    this  the  Popup  login  screen  started  to appear on the browser
    again.

    This happens because the security in Domino R5 has been  improved,
    in fact, the default  user in R5 is  not the same default  user in
    the R4, the default user in  R5 is the Lotus Notes Client  default
    user,  the  default  user  for  web  access is Anonymous, also the
    template  for  the  public  Name  and  Address Book (NAB) in R5 is
    different  than  the  NAB  in  R4,  this  change is made until you
    upgrade your applications  and your public  NAB to R5,  you can do
    it by  replicate them,  or by  typing "load  updall" at the server
    console.  So this  shouldn't be marked as  bug but as part  of the
    migration process you must run.