I have seen this issue when you configure LDAP as the Auth Source, but in
config it is still pointing to DB Backend.
Look in Sysconfig for Auth and check in Frontend::Customer::Auth set the
corresponding variables there as you have them in your Config.pm
Regards
2014-05-26 8:39 GMT-06:00 Erik va
http://stackoverflow.com/questions/1032351/how-to-write-ldap-query-to-test-if-user-is-member-of-a-group
Don't forget to enclose all your filter. (&(criteria1)(criteria2))
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Arch
Hi all,
Does anyone have an idea about this?
Is it because of the CustomerID?
Met vriendelijke groet / Kind regards / Mit freundlichem Gruß,
Erik
From: Erik van Ast
Sent: maandag 26 mei 2014 16:40
To: 'otrs@otrs.org'
Subject: Authentication succeeded, but no customer record is found in the
custo
Hi all,
When trying to log in as a customer, I get the error “Authentication succeeded,
but no customer record is found in the customer backend. Please contact your
administrator.”. Authentication works good, but apparently the information from
Active Directory does not synchronize to OTRS… Whe
ut no customer record is found
in the customer backend. Please contact your administrator."
Ok. I am going to start over from scratch with a fresh Config.pm and report
back. Brand new day. The ultimate goal would be for the site to automatically
log the user in based on the context o
ardo Certuche
Sent: Tuesday, March 19, 2013 2:03 PM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] "Authentication succeeded, but no customer record is found
in the customer backend. Please contact your administrator."
Hello Marty,
OTRS will not populate your customer_use
g] *On Behalf
> Of *Gerald Young
> *Sent:* Wednesday, March 20, 2013 11:33 AM
>
> *To:* User questions and discussions about OTRS.
> *Subject:* Re: [otrs] "Authentication succeeded, but no customer record
> is found in the customer backend. Please contact your administrato
M
To: User questions and discussions about OTRS.
Subject: Re: [otrs] "Authentication succeeded, but no customer record is found
in the customer backend. Please contact your administrator."
http://forums.otterhub.org/viewto
http://forums.otterhub.org/viewtopic.php?f=81&t=15422
On Wed, Mar 20, 2013 at 11:20 AM, David Boyes wrote:
> ** **
>
> ** **
>
> I've done this... it works nicely.
>
> ** **
>
> Goody! Is the code committed? I’ll have some VERY happy people here if it
> is.
>
> ---
I've done this... it works nicely.
Goody! Is the code committed? I'll have some VERY happy people here if it is.
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe:
I've done this... it works nicely.
On Wed, Mar 20, 2013 at 10:54 AM, David Boyes wrote:
> ** **
>
> Ok. I am going to start over from scratch with a fresh Config.pm and
> report back. Brand new day. The ultimate goal would be for the site to
> automatically log the user in based on the cont
Ok. I am going to start over from scratch with a fresh Config.pm and report
back. Brand new day. The ultimate goal would be for the site to automatically
log the user in based on the context of the user logged in to the workstation.
Adding GSSAPI support to OTRS has been on my to-do list for
roject killer.*
>>> ***
>>>
>>> ** **
>>>
>>> If the system can create the agent accounts based on settings in the
>>> Config.pm file, why would it not be able to do so with customers?
>>>
>>> **
lto:otrs-boun...@otrs.org] *On Behalf
>> Of *Leonardo Certuche
>> *Sent:* Tuesday, March 19, 2013 2:03 PM
>> *To:* User questions and discussions about OTRS.
>> *Subject:* Re: [otrs] "Authentication succeeded, but no customer record
>> is found in the customer back
alf
> Of *Leonardo Certuche
> *Sent:* Tuesday, March 19, 2013 2:03 PM
> *To:* User questions and discussions about OTRS.
> *Subject:* Re: [otrs] "Authentication succeeded, but no customer record
> is found in the customer backend. Please contact your administrator."
>
>
half
> Of *David Boyes
> *Sent:* Wednesday, March 20, 2013 12:09 AM
> *To:* User questions and discussions about OTRS.
> *Subject:* Re: [otrs] "Authentication succeeded, but no customer record
> is found in the customer backend. Please contact your administrator."
&g
nd discussions about OTRS.
Subject: Re: [otrs] "Authentication succeeded, but no customer record is found
in the customer backend. Please contact your administrator."
Come to think of it, if it does not add the customers to the database, the
feature is pretty worthless. Why validate against L
ion succeeded, but no customer record is found
in the customer backend. Please contact your administrator."
Come to think of it, if it does not add the customers to the database, the
feature is pretty worthless. Why validate against LDAP/AD at all for customers
if everything has to exist in the
st be
>> adding useless complexity.
>>
>> ** **
>>
>> *From:* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *On Behalf
>> Of *Marty Hillman
>> *Sent:* Tuesday, March 19, 2013 3:00 PM
>>
>> *To:* User questions and discussions about OTRS.
>
t; Of *Marty Hillman
> *Sent:* Tuesday, March 19, 2013 3:00 PM
>
> *To:* User questions and discussions about OTRS.
> *Subject:* Re: [otrs] "Authentication succeeded, but no customer record
> is found in the customer backend. Please contact your administrator."
>
> ** *
...@otrs.org] On Behalf Of Marty
Hillman
Sent: Tuesday, March 19, 2013 3:00 PM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] "Authentication succeeded, but no customer record is found
in the customer backend. Please contact your administrator."
My Config.pm app
] "Authentication succeeded, but no customer record is found
in the customer backend. Please contact your administrator."
Hello Marty,
OTRS will not populate your customer_user database once integrated with an
LDAP/AD. It will check if the user exists on 'CN=OTRS
Dev,OU=leve
Hello Marty,
OTRS will not populate your customer_user database once integrated with an
LDAP/AD. It will check if the user exists on 'CN=OTRS
Dev,OU=level2,OU=level1,DC=domain,DC=com' and then it will confirm the
password. If it matches, it will let the customer log in.
What you are facing proba
I have Googled and screwed around with Config.pm for hours. The configuration
is creating agents in the database appropriately, but it is not creating users
in the customer database. I am using this as in internal system only, so there
is no outside access. I want any user to be able to use t
24 matches
Mail list logo
