AR System 8.1: Why is the BMC AREA LDAP plugin not working?

[John Baker]

Curt

Yes, it makes perfect sense to move everything over to Java plugins on 
the Java plugin server. But I guess if one has been staring at the 
arplugin log for a decade, and has become accustomed to the C plugin, it 
could be confusing to look elsewhere. I also agree that it's better to 
look in one place for plugin logging than two.


Good of you to correct my understanding though :)


John

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: AR System 8.1: Why is the BMC AREA LDAP plugin not working?

[Curtis Gallant]

Hi John,

In 8.1 the default LDAP plugins are based on Java plugins but they are not
the AtriumSSO ones.  What you are basically doing here is disabling the
newer Java plugin for AREA so that it falls back to the C plugin.

The java plugin is actually arealdapplugin81_build001.jar which is supposed
to be a like for like re-write of the C plugin and have nothing to do with
the AtriumSSO ones (at least that I can see).  Once you install/integrate
in AtriumSSO this may change though but I don't have it installed so I
can't confirm if installing/integration AtriumSSO actually changes anything
about this specific plugin but doubt it as I assume it's no longer used
since instead you configure everything in AtriumSSO which is a different
story all together and I still like your plugin better :)

See here for more info:

https://docs.bmc.com/docs/display/public/ars81/Troubleshooting+AREA+LDAP+plug-in+issues

Because this is now a Java plugin, you won't see anything in the arplugin
log files, you need to check the javaplugin logs (and potentially enable
the logging itself).

Cheers,




On Fri, Mar 15, 2013 at 9:59 AM, John Baker
wrote:

> Hello
>
> When installing AR System 8.1, you may expect to be able to carry on using
> the BMC AREA LDAP plugin. It appears BMC have switched on the AtriumSSO
> AREA plugin by default, and would prefer you ran this product to achieve
> what the AREA LDAP plugin does without the overhead of extra hardware, load
> balancers, configuration nightmares, etc.
>
> If you're wondering why the BMC AREA LDAP or BMC AREA Hub plugins aren't
> working (ie why authentication events aren't going to the arplugin log
> file) search for this line in ar.cfg:
>
> Server-Plugin-Alias: AREA 
>
> and comment it out, ie.
>
> #Server-Plugin-Alias: AREA 
>
> This will send authentication events back to the C plugin server to which
> you're accustomed.
>
>
> John
>
> __**__**
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>



-- 
:wq cuga

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

AR System 8.1: Why is the BMC AREA LDAP plugin not working?

[John Baker]

Hello

When installing AR System 8.1, you may expect to be able to carry on 
using the BMC AREA LDAP plugin. It appears BMC have switched on the 
AtriumSSO AREA plugin by default, and would prefer you ran this product 
to achieve what the AREA LDAP plugin does without the overhead of extra 
hardware, load balancers, configuration nightmares, etc.


If you're wondering why the BMC AREA LDAP or BMC AREA Hub plugins aren't 
working (ie why authentication events aren't going to the arplugin log 
file) search for this line in ar.cfg:


Server-Plugin-Alias: AREA 

and comment it out, ie.

#Server-Plugin-Alias: AREA 

This will send authentication events back to the C plugin server to 
which you're accustomed.



John

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"