ejbd protocol does normally:

auth();
business();


this flag makes it logging with the request, kind of:

authThenBusiness();


It is more reliable with security frameworks cause it is compatible with
ThreadLocal often used in impls.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-06-20 16:01 GMT+02:00 amol.p.dongare <ad1@3ds.com>:

> this trick works, however
>
> before setting this property when I debug my ejbclient it was showing
> following information
> *ClientMetaData Object which shows clientIndentity (UUID) and
> ProtocolMetaData Object values*
>
> However after setting *openejb.ejbd.authenticate-with-request=true* it
> shows
> *ClientMetaData Object=null and ProtocolMetaData Object=null*
>
> What are the consequences of this? Does this mean after setting this
> property remote clients are no more authenticated during business call?
>
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/How-to-share-identity-between-several-TomEE-servers-
> tp4680280p4681927.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>