You searched for the word(s): userid:217152

More Search Options

RSS Available

• Re: DotNetNuke 2.1.2 Authentication beta 2

  When you say "sitename" is that really the machine name? If so, you are hitting the site from the in tra net zone instead of the in ter net zone, as far as IE is concerned. These zones have different security policies; the browser will automaticlly forward you authentication to an intranet site, but not an internet site. If you add your internet site to the "trusted sites" zone, they should work about the same. I believe there are still some differences (by default) that have

  Posted to DotNetNuke (Forum) by mbrandon on 7/27/2004

• Re: The best format for AD UserName in DNN database?

  I think this defeats the second largest gain to AD integration - a end user experience *without* a login box. The whole concept of single-sign-on is just that - you only enter your sign-on authentication once, at the initial point of network authentication. This allows for more "intrusive" types of logon technology, such as bio-metrics and/or strong passwords, to be more readily accepted by your user-base. (And culturally, the executive decision makers). The largest gain, in my mind, is

  Posted to DotNetNuke (Forum) by mbrandon on 6/28/2004

• Re: New version: DotNetNuke Authentication

  Search through this thread (I posted all about this), or look at my web site. I have this functioning as service running on my webserver. I'm using the older version of the code, so you might have to make changes to work with the newer. -Mark

  Posted to DotNetNuke (Forum) by mbrandon on 6/14/2004

• Re: Authentication component for DNN.2.0.4

  ingram >"I had a problem with the search engines visiting the sites when I had the authentication running. It seems that it was trying to authenticate the yahoo bot, and it was unable to visit the site. I wrote Tam, but havent heard anything. " Umm... So you have an intranet site with content that you want secured via AD, yet you want to allow an anoymous bot to sniff it? I can't quite say that I understand the logic.

  Posted to DotNetNuke (Forum) by mbrandon on 5/13/2004

• Re: SuperUser Security

  Errr... You probably don't want to set edit rights to use role -1... that is the "AllUsers" role. As I said, those are defined in Globals.vb .... -1 = AllUsers, -2 is SuperUser, -3 is unAuthenticated users. Those are Global role ID's. All other (including the Admin role for each portal- which is differnet for each portal, as I could be an admin in one portal and not another) are in the roles database. IsSuperUser should actually be a bit field - even though it is defined as an int, is functions

  Posted to DotNetNuke (Forum) by mbrandon on 5/11/2004

• Re: SuperUser Security

  First off... all my coding experiance with DNN is with the 1.0.x codebase... I haven't gotten into 2.0 yet, so any code-specific comments relate to 1.0.10e. Since one of the major changes was the inclusion of skins, the implementation may have changed some. (I am assuming from your referance to a .template file you are on 2.x) The basic functionality design hasn't changed, however - the admin/host tabs are part of the application. As such, the interface is designed to exclude them from the management

  Posted to DotNetNuke (Forum) by mbrandon on 5/11/2004

• Re: DNN2: Confused about ModuleID / PortalID

  I would say "It Depends" :) What you have to think about, is how do you want your module to react to being placed more then once on a tab, more then once in a portal, and in more then one portal. The level at which it is important you distiguish between them, is the level you want to tie your data to. ModuleID identifies a unique instance of your module, and in most cases is all you need to identify information about what data belongs with this instance - PortalID/TabID are really used

  Posted to Custom Modules (Forum) by mbrandon on 5/10/2004

• Re: SuperUser Security

  Unless you are using a module that explicitly checks to see if you are the superuser, the superuser is just a user that happens to be in all roles. You can not remove edit/view rights for the admin through the interface - it protects the portal admin from locking themselves out. So, even as the superuser, you can't remove admin rights from a item (although it seems like you should be able to!) However, since the superuser is always in all roles, all you should have to do is change the authRoleID

  Posted to DotNetNuke (Forum) by mbrandon on 5/10/2004

• Re: New version: DotNetNuke Authentication

  DNN displays a concatination of first & last name from the users table in the database in most places - sometime it displays the username, or just the first name... So, you must have data in the table for it to display. WA populates the users table for you with data in AD - The seperate AD fields GivenName & sn are used to fill FirstName & LastName fields in DNN. So, yes, the cause is that incomplete data in AD is causing you to not see information in DNN. Tha answer is to populate AD

  Posted to DotNetNuke (Forum) by mbrandon on 4/15/2004

• Re: Expanding/Contracting

  How did this go? Did you ever release this?

  Posted to Commerce Starter Kit (Forum) by mbrandon on 4/14/2004