• Type: Bug
• Resolution: Duplicate
• Priority: Medium
• Fix Version/s: None
• Affects Version/s: 1.6.1
• Component/s: Caching, Core features, Directory - LDAP
• Labels:

  • crowduser
• Environment:

  Standalone;JDK 1.5; Linux

[CWD-1857] User Added autmatically to crowd directory when user try to access an application managed in crowd

Collapse comment: joe added a comment - 10/Apr/2015 9:49 AM

joe added a comment - 10/Apr/2015 9:49 AM

I believe this is the same underlying problem as CWD-2650. I'm closing this as that ticket has more details.

Expand comment: joe added a comment - 10/Apr/2015 9:49 AM

joe added a comment - 10/Apr/2015 9:49 AM I believe this is the same underlying problem as CWD-2650 . I'm closing this as that ticket has more details.

Collapse comment: Gaurav Tomer added a comment - 23/Mar/2010 4:56 AM

Gaurav Tomer added a comment - 23/Mar/2010 4:56 AM

What I want to say is that the user which is not member of Application 'Y' and Directory 'X', if try to access 'Y' is should not be added to 'X' automatically but it should be added to 'X' by crowd administrator.

Let me clear the point with this example:

I added JIRA as an application to Crowd and the directory configured for this application is Delegated authentication directory which is integrated to LDAP server. Now a new person try to access JIRA using his LDAP credential but as he is not a member of the directory/Application(JIRA) and he will fail to login, but if you we go and search that person in the application Directory inside crowd we can see that he has been added to that directory automatically, but he still not be able to login because he is not part of jira-user group which crowd admin have to do manually ( we are using crowd version 1.6.1 - Planning to migrate to 2.*).

So my issue is that person details shouldn't be added to the directory once he tries to login to an application managed by crowd

I hope my point is clear now

Expand comment: Gaurav Tomer added a comment - 23/Mar/2010 4:56 AM

Gaurav Tomer added a comment - 23/Mar/2010 4:56 AM What I want to say is that the user which is not member of Application 'Y' and Directory 'X', if try to access 'Y' is should not be added to 'X' automatically but it should be added to 'X' by crowd administrator. Let me clear the point with this example: I added JIRA as an application to Crowd and the directory configured for this application is Delegated authentication directory which is integrated to LDAP server. Now a new person try to access JIRA using his LDAP credential but as he is not a member of the directory/Application(JIRA) and he will fail to login, but if you we go and search that person in the application Directory inside crowd we can see that he has been added to that directory automatically, but he still not be able to login because he is not part of jira-user group which crowd admin have to do manually ( we are using crowd version 1.6.1 - Planning to migrate to 2.*). So my issue is that person details shouldn't be added to the directory once he tries to login to an application managed by crowd I hope my point is clear now

Collapse comment: Justin Koke added a comment - 22/Mar/2010 11:14 PM

Justin Koke added a comment - 22/Mar/2010 11:14 PM

Just to be clear here, what you are saying is that you do not want users to be added to Directory 'X', is this correct?

Expand comment: Justin Koke added a comment - 22/Mar/2010 11:14 PM

Justin Koke added a comment - 22/Mar/2010 11:14 PM Just to be clear here, what you are saying is that you do not want users to be added to Directory 'X', is this correct?

Collapse comment: Gaurav Tomer added a comment - 22/Mar/2010 8:55 AM

Gaurav Tomer added a comment - 22/Mar/2010 8:55 AM

Please let me know the solution for this

Expand comment: Gaurav Tomer added a comment - 22/Mar/2010 8:55 AM

Gaurav Tomer added a comment - 22/Mar/2010 8:55 AM Please let me know the solution for this