Hi, I use v3.3 with the default db backend for customer login and need to integrate it with an in-house-built customer experience portal (view reports/bills/marketing materials/etc.).
The customer should login only once (in the portal) and then seamlessly jump between the portal and OTRS. The OTRS authentication & session lifetime should be settled transparently behind the scenes between the systems (i.e. log out / switch id from portal => same in OTRS). QUESTION: Is there an authentication module in OTRS or in Apache which could be tweaked to create this integration against our new portal? Thanks, Bogdan P.S: OTRS' manual points to Kernel::System::Auth::HTTPBasicAuth which seems to rely on Apache doing the authentication. I know nothing about this approach but if someone would tell me that it supports log out / switch id in OTRS when customer does that in our portal, I would look into it. I also found this http://developer.aaiedu.hr/faq/11.html ~ solution for v3.0 that integrates with a custom-built PHP SAML provider. I could modify it to use a [custom] NET provider but I would end up with a very expensive solution.
--------------------------------------------------------------------- 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
