Another question about the group sync.
What is the AccessAttr and what are the possible parameters?
$Self->{'AuthSyncModule::LDAP::AccessAttr'} = 'memberUid';
Is the parameter for this setting an ldap attribute?
Rory
Support my 365 Challenge in aid of the Irish Cancer Society
www.365challenge
Nuts, hit send too early.
So I've added the following to the config;
# Sync LDAP group to role in OTRS
# AuthSyncModule::LDAP::UserSyncRolesDefinition
$Self->{'AuthSyncModule::LDAP::UserSyncRolesDefinition'} = {
# ldap group
'CN=IT,OU=Groups,OU=IT,OU=Departments' => {
Hi Michiel,
Thanks for the info. I'm trying to use the SyncRolesDefinition and
I've added the following to the config;
# Sync LDAP group to role in OTRS
# AuthSyncModule::LDAP::UserSyncRolesDefinition
$Self->{'AuthSyncModule::LDAP::UserSyncRolesDefinition'} = {
# ldap group
Hi Rory and Mauricio,
Let me first state that if you have configured the AuthSyncModule the
OTRS will sync agent data every time a user logs in to OTRS. If you'd
change the user properties in active directory; they would be updated
in OTRS as soon as the agent logs in.
And of course, if the accoun
2009/8/6 Mauricio Tavares :
> I have no problems if otrs cannot edit ldap. What I would like is to
> be able to define which group someone belongs to in ldap and then otrs will
> see the groups memberships and then grant the said user rights according to
> the memberships.
I'm kinda guessi
Rory wrote:
2009/8/5 Mauricio Tavares :
So, otrs is only using ldap to check the passwords? Is the
access/ownership info (i.e. who belongs to which group and can do what kind
of harm) stored in the local DB then? I guess it has to since the
documentation states otrs only does read only
2009/8/5 Mauricio Tavares :
> So, otrs is only using ldap to check the passwords? Is the
> access/ownership info (i.e. who belongs to which group and can do what kind
> of harm) stored in the local DB then? I guess it has to since the
> documentation states otrs only does read only access
Rory wrote:
I had some confusion with this recently too.
As I understand it, you can have either DB or LDAP authentication for
agents, not both.
Oh lovely. I guess that explains why I cannot login even as the
root/localhost user.
The way OTRS authenticates is by checking the user against it
I had some confusion with this recently too.
As I understand it, you can have either DB or LDAP authentication for
agents, not both.
The way OTRS authenticates is by checking the user against its own
database. Once the user exists in its database it will authenticate
the user against the LDAP dire
I am trying to have otrs to have some of my agents defined in ldap. So,
I set /etc/otrs/Kernel/Config.pm as follows:
# Authenticate agents against LDAP backend
$Self->{'AuthModule'} = 'Kernel::System::Auth::LDAP';
$Self->{'AuthModule::LDAP::Host'} = 'ldap-pserver.internal.domain.co
AccountName', 'cn', 'mail'],
CustomerUserSearchPrefix => '',
CustomerUserSearchSuffix => '*',
CustomerUserSearchListLimit => 250,
CustomerUserPostMasterSearchFields => ['mail'],
CustomerUserNameFields => [
I've just got OTRS 1.3.1 installed want to use my existing
OpenLDAP server as a Customer back-end and User authentication. It
requires TLS connections. Does anyone have an example of the LDAP
config part of Config.pm using LDAP/TLS?
Thanks,
Jason Joines
=
12 matches
Mail list logo
