[ http://jira.jboss.com/jira/browse/JBPORTAL-1592?page=all ] Boleslaw Dawidowicz reassigned JBPORTAL-1592: --------------------------------------------- Assignee: Boleslaw Dawidowicz -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1592?page=all ] Boleslaw Dawidowicz resolved JBPORTAL-1592. ------------------------------------------- Resolution: Cannot Reproduce Bug I'm closing this. If you can assert that following filter isn't working please reopen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1592?page=all ] Tobias Roth reopened JBPORTAL-1592: ----------------------------------- Maybe I am misunderstanding something, but I still think there is a bug around. The filter you posted works and all, but in a real-world scenario, that's not what one would use for a filter. The filter is constructed by the code, one would not directly add LastName, FirstName for a filter, or only that specific user would be found. If you look at the log snippets I pasted in a previous post, here is what happens: The user enters his credentials in the login box. The code finds the record for that user, and from that record, it takes the DN. From that DN (which may contain a comma), it constructs the search filter to search for roles. Now, if the DN does contain a comma, no roles are found, because the code does not escape the comma correctly. There is no way I can fix this by adapting the filters in my config, or am I missing something? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1592?page=comments#action_1237... ] Tobias Roth commented on JBPORTAL-1592: --------------------------------------- No problem about the answering delay, it's not like you have an SLA with me :-) I admit the problem is getting a bit confusing, I had to look through the whole forum post again myself. On top of that, I had a weird bug and couldn't start my portal anymore. I tried everything to find the cause of the problem, and then, just because I ran out of ideas, I reinstalled my jdk, and things worked again. D'oh. Anyway, I'll try to explain my problem in different words (I'll also attach example files). I am using your ldif, the one with the jdukes you posted in the forum thread. I made a small modification: I removed the backslash and comma for jduke4, so I have a user to check if everything works without a comma. Now, there are several jdukes, all of them with a comma in their name except my control user, jduke4. All of them are member of the "User" group. I have this userSearchFilter: (&((uid={0})(objectClass=person))) And this roleSearchFilter: (&((member={1})(objectClass=groupOfNames))) With these filters, all jdukes can log in, but roles are only found for jduke4 (who has no comma in his DN), not for the other jdukes (who all have commas). Escaping the comma with three backslashes in the roleSearchFilter is all very well, but I cannot do that, because I want a filter that finds all jdukes, not just a specific one. It is that part of the jboss portal code that substitutes the {1} from the roleSearchFilter with does not properly escape commas, in my opinion. I hope I could make this a bit more clear, it is indeed difficult to explain. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1592?page=all ] Tobias Roth updated JBPORTAL-1592: ---------------------------------- Attachment: ldap_identity-config.xml ldap configuration to show problem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1592?page=all ] Boleslaw Dawidowicz resolved JBPORTAL-1592. ------------------------------------------- Resolution: Done fixed. commited to JBoss_Portal_Branch_2_6. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira