Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD Authentication and child portalsAD Authentication and child portals
Previous
 
Next
New Post
4/13/2011 5:23 PM
 
The username is displayed that way by design. I'm not sure of the original reason as it was there when I took over the project as it makes sense in a intranet/internet situation and shouldn't be the cause of the user not being added to the group correctly (in all my testing). DNN just sees the AD user as any generic user that happens to have a \ in their username.
 
New Post
4/14/2011 8:47 AM
 
Ok, if that display is by design; It's not very helpful when running DNN in AD integrated mode because all the users are listed under the letter of the alphabet that your domain begins with. Not a big deal.

So I am left with the original problem. I have a pre-existing user, who is part of a pre-existing AD group. I gave this group rights within the child portal (by creating the group with the same name in the portal and granting the group view rights to a series of pages) and the user has not yet been added to the group. I have synchronize roles checked in the AD extension setup.
 
New Post
4/14/2011 9:16 AM
 
If the display name is that way by design, that's fine. It's not very helpful when running in AD mode, as all the users are listed under the letter of the alphabet the domain name begins with.

I am left with the problem of an existing group and an existing user. When I assigned the group to the child portal (by creating a new role with the same name) and granting that role view rights to some pages, users are not being auto added to the role in the child portal. I definitely have Synch Roles checked in the AD extension setup. Any suggestions as to what to try?
 
New Post
4/14/2011 9:16 AM
 
If the display name is that way by design, that's fine. It's not very helpful when running in AD mode, as all the users are listed under the letter of the alphabet the domain name begins with.

I am left with the problem of an existing group and an existing user. When I assigned the group to the child portal (by creating a new role with the same name) and granting that role view rights to some pages, users are not being auto added to the role in the child portal. I definitely have Synch Roles checked in the AD extension setup. Any suggestions as to what to try?
 
New Post
4/14/2011 11:18 AM
 
I know it's a pain and I've looked at trying to change it but would require some external scripting to adjust current usernames. Also in mixed mode or multi-domain environments it could lead to even bigger problems. If anyone has a solution I'm more than open to it. As for your existing problem.... I'll have to do some testing to see if I can recreate the problem on a consistent basis so that I can try to debug the code. Without that I've got nothing. Is it just one particular user or is it multiple users?
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD Authentication and child portalsAD Authentication and child portals


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out