We are implementing Ess/Mss on 8.03 msp 7 enviro and 8.1 msp 5 apps.
I'm struggling with only one item on my security plan. I had planned to leave the login field in rd30 blank for all ess/mss users (portal application users will have a separate logon for their other access..so they are not an issue). The default users has to have wide open security for ess/mss to work, so I've grouped all ess/mss users and attached to a custom xml file that took away the search box. But, if we ever add an rd30 w/o the login info and forget to secure them with the custom xml file...they have WIDE OPEN SECURITY and that can't be good. So I either want to make the defaul.xml the locked down one or attach all ess/mss users to a different logon ('emssuser') and leave Mr. Default user with zero access.
Any ideas on this. I did research on the forums and could not locate the post, but one person stated that gsc did not recommend attaching mass users to a different login besides the default user but they did not state why. I also saw a post about a limitation to rmid of 1000 users and i'm not sure what that means or if it affects me).
I also have to consider that we will be going to lsf 9.0 next year and then apps 9.0 the following year and how my plan will convert over.
Any help is appreciated and sorry that I could not attach this to a similar post..I kept getting locked up when I tried to do a search to re-locate the prior posts.