It works !!!

Many thanks and best regards to you,

Franck

-----otrs-bounces@otrs.org a écrit : -----

Pour : "User questions and discussions about OTRS.org" <otrs@otrs.org>
De : Alexander Scholler <alexander.scholler@augsburg.de>
Envoyé par : otrs-bounces@otrs.org
Date : 21/09/2006 12:25PM
Objet : Re: Réf. : Re: Réf. : Re: Réf. : Re: Réf. : Re: [otrs] LDAP Customer Backend Authentification Question

Hi Franck,

modify from
Map => [
[ 'UserLogin', 'Username', 'uid', 1, 1,
'var', '', 0 ],
to
[ 'UserLogin', 'Username', 'mail', 1, 1,
'var', '', 0 ],
within $Self->{CustomerUser}.

I think that's it.

FYI: I wrote the following before I noticed the above described
misconfiguration.
...

It's quite difficult to do analysis from far away ;-)

franck.lamas@stp-presse.fr schrieb:
> Hi,
>
> I did what you suggested.
>
> When creating a new ticket, I can choose the customer and the customer
> number is the mail address.
>
> The customer can login with his mail address.
>
> But he don't see any tickets.
> Two reasons :
>
> - the fied customer_user_id is always the uid (put by the CreateTicket),
> not the mail address

That must not be! The customer-mail-address has to be stored in
ticket.customer_user_id. Otherwise, the ticket is not recognized of
belonging to the customer who is logged in with his mail-address.

>
> - Even if I change the fields in the ticket table, the customer don't
> see his tickets.
>
> Find attached my new config.pm.

Looks good.

Login as customer and watch your logfile.
On my system, I get
[Thu Sep 21 12:16:24
2006][Notice][Kernel::System::CustomerAuth::LDAP::Auth] CustomerUser:
alexander.scholler@augsburg.de authentification ok

I think this means that the customer is managed with his mail-address as
ID within the Customer-WebGUI.

>
> I'm stucked !!!
> -----otrs-bounces@otrs.org a écrit : -----
>
> Pour : "User questions and discussions about OTRS.org" <otrs@otrs.org>
> De : Alexander Scholler <alexander.scholler@augsburg.de>
> Envoyé par : otrs-bounces@otrs.org
> Date : 21/09/2006 06:54AM
> Objet : Re: Réf. : Re: Réf. : Re: Réf. : Re: [otrs] LDAP Customer
> Backend Authentification Question
>
> Hi Franck,
>
> I can't follow your Config.pm
>
> * You defined twice $Self->{CustomerUser}
> * In both, $Self->{CustomerUser} and
> $Self->{'Customer::AuthModule::LDAP...
> you use uid instead of mail.
>
> With a quick view over your config, I suggest the following on lines:
>
> 272: CustomerKey => 'mail',
> 216: $Self->{'Customer::AuthModule::LDAP::UID'} = 'mail';
> 110-171: delete these lines
>
> That could result in the fact that
> * customers can login with their mail-address instead of uid
> * can view NEW created tickets
>
> Further, you have to do the discribed DB-changes to include the old
> tickets...
>
> Bye, Alex
>
> franck.lamas@stp-presse.fr schrieb:
> > Please find attached the config.pm file. We are running OTRS on a
> > windows 2003 server using the full package installation, ruuning
> on a
> > mysql database.
> >
> >
> > -----otrs-bounces@otrs.org a écrit : -----
> >
> > Pour : "User questions and discussions about OTRS.org"
> <otrs@otrs.org>
> > De : Alexander Scholler <alexander.scholler@augsburg.de>
> > Envoyé par : otrs-bounces@otrs.org
> > Date : 20/09/2006 02:51PM
> > Objet : Re: Réf. : Re: Réf. : Re: [otrs] LDAP Customer Backend
> > Authentification Question
> >
> >
> > Hi, post some details: your configuration, ...
> >
> >
> > franck.lamas@stp-presse.fr schrieb:
> > > I understand that the old tickets may become "invisible"
> after the
> > > change. But I tried to create the new tickets and the user
> don't see
> > > them even if the contents of the two fields customer_id and
> > > customer_user_id are different.
> > >
> > > May be I missed something...
> > >
> > > -----otrs-bounces@otrs.org
> <mailto:-----otrs-bounces@otrs.org> a
> > écrit :
> > > -----
> > >
> > > Pour : "User questions and discussions about OTRS.org"
> > <otrs@otrs.org>
> > > De : Alexander Scholler <alexander.scholler@augsburg.de>
> > > Envoyé par : otrs-bounces@otrs.org
> > > Date : 20/09/2006 10:36AM
> > > Objet : Re: Réf. : Re: [otrs] LDAP Customer Backend
> > Authentification
> > > Question
> > >
> > > Hi Franck,
> > >
> > > franck.lamas@stp-presse.fr schrieb:
> > > > Well, I tried what you said, and the user can login
> with
> > the mail
> > > > address. The problem is that they don't see any
> tickets !
> > > >
> > > > As I use also LDAP for the customer database
> backend (on the
> > > AgentTicket
> > > > Form), I think I have to coordinate the twice
> things, but
> > I don't
> > > know
> > > > how to do it.
> > >
> > >
> > > As written before, you have to set
> > > >> $Self->{CustomerUser} = {
> > > >> # ...
> > > >> CustomerKey => 'mail',
> > > >> # ...
> > > >> }
> > > to tell OTRS to use the mail-address as unique
> customer id.
> > >
> > > Note that through your switch of identification from
> uid to
> > mail, your
> > > OTRS-data perhaps may get inconsistent. But I think not in
> > such a way
> > > that you shall not switch the customer-identification.
> > >
> > > >
> > > > I had a look in the Ticket table and I've noticed
> that the
> > > customer_id
> > > > and the customer_user_id are used to list the
> tickets by
> > > customer. But
> > > > if I make changes in the table it doesn't work...
> > >
> > > It works, believe me - you made some other mistake.
> > >
> > > Bye, Alex
> > >
> > > >
> > > >
> > > > -----otrs-bounces@otrs.org a écrit : -----
> > > >
> > > > Pour : "User questions and discussions about
> OTRS.org"
> > > <otrs@otrs.org>
> > > > De : Alexander Scholler
> <alexander.scholler@augsburg.de>
> > > > Envoyé par : otrs-bounces@otrs.org
> > > > Date : 20/09/2006 07:06AM
> > > > Objet : Re: [otrs] LDAP Customer Backend
> Authentification
> > > Question
> > > >
> > > > Hi,
> > > >
> > > > franck.lamas@stp-presse.fr schrieb:
> > > > > I use LDAP to let my customers authentificate in
> > the system.
> > > > >
> > > > > My users have to enter their userid and i'd
> prefer that
> > > they have to
> > > > > enter their mail address. How can I achieve
> this ?
> > > >
> > > > $Self->{'Customer::AuthModule::LDAP::UID'} =
> 'mail';
> > > > $Self->{CustomerUser} = {
> > > > # ...
> > > > CustomerKey => 'mail',
> > > > # ...
> > > > }
> > > >
> > > > # optional
> > > > $Self->{'Customer::AuthModule::LDAP::UserSuffix'} =
> > > > '@yourmaildomain.tld';
> > > >
> > > > (That works fine on our installation.)
> > > >
> > > > I think that the OTRS-login-name of the
> customer (you
> > wish to
> > > use the
> > > > mail-address) must be identical to the unique
> > Identification
> > > of the
> > > > customer (CustomerKey) within OTRS. I think you can
> > not do any
> > > > mapping like
> > > > 1) login with mail-adress,
> > > > 2) map mail-address to uid and use customer-uid
> within
> > OTRS
> > > >
> > > > >
> > > > > Thanks in advance
> > > > > Franck
> > > >
> > > > Bye, Alex
> > > > _______________________________________________
> > > > 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
> > > > Support orr consulting for your OTRS system?
> > > > => http://www.otrs.com/
> > > >
> > > >
> > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------
> > > >
> > > > _______________________________________________
> > > > 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
> > > > Support orr consulting for your OTRS system?
> > > > => http://www.otrs.com/
> > >
> > > _______________________________________________
> > > 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
> > > Support orr consulting for your OTRS system?
> > > => http://www.otrs.com/
> > >
> > >
> > >
> > >
> >
> ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > 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
> > > Support orr consulting for your OTRS system?
> > > => http://www.otrs.com/
> >
> > _______________________________________________
> > 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
> > Support orr consulting for your OTRS system?
> > => http://www.otrs.com/
> >
> >
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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
> > Support orr consulting for your OTRS system?
> > => http://www.otrs.com/
>
> _______________________________________________
> 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
> Support orr consulting for your OTRS system?
> => http://www.otrs.com/
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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
> Support orr consulting for your OTRS system?
> => http://www.otrs.com/

_______________________________________________
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
Support orr consulting for your OTRS system?
=> http://www.otrs.com/