I'm sure the best way to implement it is to not let the LDAP driver in
Kernel::System::CustomerUser::LDAP die if it can not connect. If you
would add that functionality, I'm sure we'd be open to accept such
patches!
--
Mike
On Sun, Sep 23, 2012 at 6:04 PM, Stefano Ricci
ok, from your response, i understand that the script in config.pm are
executed on new incoming event.. i thnik that these events are:
- new email fetched
- customer login
- agent login
is that correct?
On 22 September 2012 23:52, Gerald Young cryth...@gmail.com wrote:
It may be
I wouldn't *exactly* use the terminology event for this purpose.
Essentially, you may be correct, but Config.pm is a module that is
accessed to provide configuration attributes according to how
Config.pm evaluates the expression for a given variable or
attribute. Config.pm is being used
ok, thanks for the response.
now i test the ping control, and if generate problem...
On 23 September 2012 17:03, Gerald Young cryth...@gmail.com wrote:
I wouldn't *exactly* use the terminology event for this purpose.
Essentially, you may be correct, but Config.pm is a module that is
accessed
hi to all... i user otrs 3.1.7 to work with my company customer and today i
have some problems.
my configuration is that: otrs in datacenter connected with customers
active directory throught vpn connections and, if the customer is small,
only the local database.
today the vpn connection go down
It may be possible to do that as Config.pm is perl ... How? You'd
have to search for Net::Ping or query the LDAP module itself to set
the auth method based upon the LDAP availability.
On Sat, Sep 22, 2012 at 1:13 PM, Stefano Ricci
stefano.ri...@riccimatic.com wrote:
hi to all... i user otrs
