Last post Dec 22, 2005 11:58 AM by thomasson6
Dec 22, 2005 09:13 AM|thomasson6|LINK
I'm currently working on an extranet for a customer that is only going to provide an IP address to their users and the site will never have a domain assigned. The site is 'very' sensitive and my customer does not want any information presented to the user
until they sign-in. This includes 'logo', 'header', and 'footer' information. Since the logo, header, and footer are not modules, I was wondering if there was anyway to notify DNN not to display 'anything' until the user is signed in to the portal. I basically
want to display the login module and nothing else when they go to the portal. Any ideas??
Also, there is a requirement to have 'sub-admin' users add 'new users' into the portal. The 'sub-admin' users require a subset of the functions that are currently assigned to the Admin user. I'm not aware of any security options that would allow me to
create such a user. Any ideas??
Dec 22, 2005 11:12 AM|oziweb|LINK
create a "skinless" skin for the home page - on this "home" page put your login module only.
by a skinless skin I mean a skin with no header no footer ,no menu and no logo. The only thing the skin needs is a contentPane Set the security of this page to public - set the security of every other page to the required securiy roles.
You will need the redirect module to redirect the loged in users to the true home page. There was a PA for DNN2 that did this from spohnSoftware called SignInRedirect they may have a DNN3 version. The dnn2 came with source for free. You could simply mod
the login module code to redirect to the true home page.
The sub admin problem is really not a problem - simply setup the security roles correct and it will work. You can move the functions within the admin menu to any where you want or simply remove them a simple and fast method is to make the changes directly
to the database tables ie in the tabs table you can hide any of the admin functions and change their authorized roles. In the modules table you can do this for the individual modules (backup the database before you make the changes)
You can also clone the manageusers files and create a new pa that you can then assign what ever security roles you need.( this would be the recommended method rather then directly changing the database values) however directly changing the values in the
database does not require a recompile.
Dec 22, 2005 11:44 AM|MobileNow|LINK
Dec 22, 2005 11:56 AM|thomasson6|LINK
'skinless' skin, great terminology and great idea. Thanks.
I figured I could change the database to handle the sub-admin problem. I'm thinking of going with a PA to handle my requirements. I don't like changing the base.
Dec 22, 2005 11:58 AM|thomasson6|LINK
We figure that there will be 'people' that will be able to find out some information about the site but they won't be able to figure out the purpose. The logo and other header information would provide them with the 'reason' for the site and my client wants
to be sure that his can not happen.
'skinless' skin seems to be the way to go.