No. I do this all the time. Sso, even.
On Mar 20, 2013 9:16 AM, "Marty Hillman" <mhill...@equuscs.com> 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 context of the user logged in to
> the workstation.  This would allow me to embed the customer.pl page (more
> specifically a new ticket form) directly into SharePoint (gasp!) so that we
> have full integration within our intranet.  Again, there will be no access
> for non-employees as this is exclusively internal facing.  Am I being too
> unrealistic?****
>
> ** **
>
> Thanks for all of the pointers everyone.  I will use these links to try
> again and let you know.****
>
> ** **
>
> *From:* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *On Behalf
> 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."****
>
> ** **
>
> Authentication and authorization are two different things (one is “can you
> access this system”, the other is “what are you allowed to do”). I agree
> that on first authentication, OTRS should create a stub record in the
> database for the authorized entity, but I actually think the “no privileges
> until explicitly assigned” is a good thing in that you don’t accidentally
> disclose things that that customer has no business seeing. ****
>
> ** **
>
> I think the compromise approach would be to use the authorization exit to
> check whether the customer is in the database and then add a default entry
> from a site-assigned template (queue access, permissions, etc). ****
>
> ** **
>
> *From:* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *On Behalf
> Of *Marty Hillman
> *Sent:* Tuesday, March 19, 2013 4:06 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."****
>
> ** **
>
> 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 database?  That would just be
> adding useless complexity.****
>
> ** **
>
> ---------------------------------------------------------------------
> 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
>
---------------------------------------------------------------------
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

Reply via email to