I am very consious that this isn't an easy to install package .... sorry the problem is both the need to change the web.config (including having an account to logon to Active Directory) and then having to change IIS authentication.
i don't think i can do anything about the second one, and I am concerned that writing the settings into the web.config at install is the quickest way to bork the umbraco installation.
If anyone has any views on how to do this better, or indeed if this whole thing could be done better please comment.
The only problem I've struck is getting the "domainPath" in the role provider config correct. I've tried every combination I've used in the past but just can't nail it.
I usually setup a connection string in my web.config with the LDAP path similar to; LDAP://domaincontroler/OU=xxx,DC=mydomain,DC=gov,DC=au
What format should I use for the domainPath in your package?
Apart from this problem I found your instructions pretty easy to follow and preffered to do it manually rather than have it automated.
After a bit of fiddling around and looking at the source code I've sorted out my problem.
In the ADRoleProvider class (line 99) it is looking for "domain" configuration option and the example in the documentation has "domainPath". So I changed the role provider config and it all started to work.
yeah, someone else spotted that, I've updated the documentation. and I'm going to look at the Post Installer Actions so that the provider is added to the web config, but not set as default.
Glad you got it working, would be intrested to know how it goes.
Easy or way to hard
I am very consious that this isn't an easy to install package .... sorry the problem is both the need to change the web.config (including having an account to logon to Active Directory) and then having to change IIS authentication.
i don't think i can do anything about the second one, and I am concerned that writing the settings into the web.config at install is the quickest way to bork the umbraco installation.
If anyone has any views on how to do this better, or indeed if this whole thing could be done better please comment.
Hi Kevin
The only problem I've struck is getting the "domainPath" in the role provider config correct. I've tried every combination I've used in the past but just can't nail it.
I usually setup a connection string in my web.config with the LDAP path similar to; LDAP://domaincontroler/OU=xxx,DC=mydomain,DC=gov,DC=au
What format should I use for the domainPath in your package?
Apart from this problem I found your instructions pretty easy to follow and preffered to do it manually rather than have it automated.
Regards
Evan
Hi Kevin
After a bit of fiddling around and looking at the source code I've sorted out my problem.
In the ADRoleProvider class (line 99) it is looking for "domain" configuration option and the example in the documentation has "domainPath". So I changed the role provider config and it all started to work.
Cheers
Evan
yeah, someone else spotted that, I've updated the documentation. and I'm going to look at the Post Installer Actions so that the provider is added to the web config, but not set as default.
Glad you got it working, would be intrested to know how it goes.
Kevin (or anyone else), can you confirm what the correct format was for the "domain" config setting?
Thanks!
Mike, on our setup the domain is the netbios name (so domain not domain.dns.name.com)
is working on a reply...