Hi All, I'm having a little trouble with an installation of OTRS2 on Debian etch - especially I'm trying to get my customers' userdata from an Active Directory, and something seems to go wrong there (I get "Panic! No UserData!" on login..) So I thought "Hey, would be a great idea to enable debug!" and I set $Self->{'Debug'} = 5; in Config.pm. Now the first odd thing is that at the actual logging location (I'm using the File-Log) no debug messages appear, I only get lines like these: [Wed Dec 3 10:05:12 2008][Notice][Kernel::System::Auth::LDAP::Auth] User: username (CN=changed,OU=to,OU=protect,DC=the,DC=innocent) authentication ok (REMOTE_ADDR: 172.17.xxx.xxx). [Wed Dec 3 10:05:12 2008][Notice][Kernel::System::User::GetUserData] Panic! No UserData for user: 'username'!!! In my apache's error log I seem to get some debug output, e.g.: Debug: Config.pm ->Get('CGILogPrefix') --> OTRS-CGI Debug: Config.pm ->Get('SystemID') --> 01 Debug: Config.pm ->Get('LogModule') --> Kernel::System::Log::File Debug: Config.pm ->Get('LogModule::LogFile') --> /var/log/otrs/otrs.log Debug: Config.pm ->Get('LogModule::LogFile::Date') --> 0 Error: Config.pm No value for 'LogModule::LogFile::Date' in Config.pm found! ... ... ... Debug: Config.pm ->Get('Frontend::Output::PostFilter') --> Error: Config.pm No value for 'Frontend::Output::PostFilter' in Config.pm found! Debug: Config.pm ->Get('Frontend::Output::PostFilter') --> Error: Config.pm No value for 'Frontend::Output::PostFilter' in Config.pm found! These are the last lines of the debug output. Although there are some errors, these seem not to be critical, since I am able to log in as admin. I actually would expect the debug mode to give me a little debug output on what actually happens, not only on how it was able to load the configuration. Is there something wrong with my debug output? Kind regards, Lukas Barth
Hi All,
I'm having a little trouble with an installation of OTRS2 on Debian etch
On Wed, 03 Dec 2008 10:18:49 +0100, Lukas Barth
especially I'm trying to get my customers' userdata from an Active Directory, and something seems to go wrong there (I get "Panic! No UserData!" on login..) [ Snip ]
By the way, if that helps: If I log in as administrative user, and access "Customer User" in the administrative panel, search for a user, and click this user so that his data is being loaded into the "Update this user"-fields, this works perfectly - so actually OTRS should be able to load the data? Kind regards, Lukas Barth
Den 03/12/2008 kl. 13.04 skrev Lukas Barth:
By the way, if that helps: If I log in as administrative user, and access "Customer User" in the administrative panel, search for a user, and click this user so that his data is being loaded into the "Update this user"-fields, this works perfectly - so actually OTRS should be able to load the data?
You are aware that your users need to login to a different web page, right? Agents log in to "index.pl". Users log in to "customer.pl". -- Lars Jørgensen Gyldendal IT tlf. 33 75 57 96
Hi Lukas, Den 03/12/2008 kl. 10.18 skrev Lukas Barth:
I'm having a little trouble with an installation of OTRS2 on Debian etch - especially I'm trying to get my customers' userdata from an Active Directory, and something seems to go wrong there (I get "Panic! No UserData!" on login..)
This is a very common error, probably due to lacking documentation. I'll break it down for you: 1: OTRS has USERS and AGENTS. These are different. USERS er the people creating the tickets, AGENTS are the people solving them. 2: Both USERS and AGENTS can authenticate via LDAP. 3: AGENTS needs to exist in the OTRS database as well as in LDAP. 4: USERS don't need to exist in the OTRS database. So if you get the "Panic! No Userdata!" it means that your AGENT authenticated just fine via LDAP, but the AGENT was not found in the local OTRS database. You need to add that person manually to OTRS, with the same login as in the Active Directory. Fill in everything, but leave the password blank. -- Lars
participants (2)
-
Lars Jørgensen -
Lukas Barth