You can't do it per ldap, but you can do it via ACL for something that ldap
knows.
For instance, let's say you have UserLogin mapped to userPrincipalName
instead of sAMAccountName (highly recommended if you are expecting
collisions between usernames accross the different backends).
userPrincipalName would be username@login-domain
Include userPrincipalName where you see: CustomerKey => 'sAMAccountName',
and in the map
'UserLogin', 'Username', 'userPrincipalName'
Then you can employ an ACL in Config.pm like this:
$Self->{TicketAcl}->{'Unique-Descriptive-Name-for-ldap1'} = {
Properties => {
CustomerUser => {
UserLogin => ['[RegExp]login-domain$'],
},
},
Possible => {
Ticket => {
Queue => ['Queue1', 'Queue2'],
},
},
};
http://doc.otrs.org/3.1/en/html/ch18s03.html
(This is not tested. It should work according to documentation, but may
have a syntax error.)
Use at your own risk. Changing the sAMAccountName to userPrincipalName
could make old tickets for a given username inaccessible unless you use
Generic Agent to mass update: find old tickets with username x set
username= x@domain. Of course, if you've already had username collisions,
this would be a problem.
Regards,
Gerald
On Mon, Jul 16, 2012 at 4:05 AM, Stefano Ricci wrote: hi to all.... i have this problem.... segregate customers to particolare
queues... now i see that is impossible in the same istance.... but, it's possible,
in the config.pm, the possibility to HIDE the queue in function of the
login... for example... the user CUSTOMER1 logged in with active direcotry
MYDOMAIN, have to see only in the web interface the queue1 and queue3.... ---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs