I have my Intranet runnign nicely with Active Directory.  Here's my issue.  When a User clicks to "Automatically Login", it grabs their credentials and logs them in just fine, however, when I look at the Users module, I see them with their network Username, but it is appended with the Domain, in my instance the domain is PWCPA.  So, when they login, they are also, now Users of the DNN, and it shows a User as:  PWCPA/markgordon

When I want to add someone to a Role, I cannot add just their Username of markgordon, I have to add the entire DOMAIN as well.

Is there a way to get rid of the domain and the slash that follows?

Thanks!

Mark

I don't know the answer to that question, but Mike Horton has been helpful answering questions. The one site that I am using with AD still has a problem with automatic login.

Unfortunately, there isn't any easy way to accomplish this.  Per AD and windows, when you log into a pc, you need to specify your domain to differentiate from logging into the *that* machine, as opposed to logging in to the *domain* of which that machine is a member.

You could code something that interrupts the login and appends the domain where necessary, but it sure doesn't seem to be worth the trouble to deal with all of that.

Hi,

I have got AD working with DNN and the roles are syncing up. However this only seems to happen the first time you hit the site. If changes are made to AD after that, it doesnt pick them up untill you delete your cookies. I havent tried leaving it for an hour before trying again, which is my next step, however my question is, does the cookie that gets created expire, if so does anyone know after how long. If not, is anyone aware of another solution to this problem?

Thanks

Kev

I don't know the answer, but I do suggest asking over on the DotNetNuke Authentication forum.  Mike Horton is quite good at fielding questions, and you should expect to hear from him within a day.

If AD uses the login cookie, though, that's a good reason to let it expire regularly.  I think that the default is one hour.

Yeah, I got a reply off Mike last night, he said the authentication cookie takes about an hour before it goes through the process again, and that the exact time is unknown as it seems to vary from 30 minutes up to an hour. The cookie is controlled by IIS.

Thanks.