Amy Roh wrote:
Remy Maucherat wrote:
Well, I think it is perfectly acceptable, sorry ;-)
BTW, there's no CoyoteRequestFacade.recycle, that's in CoyoteRequest,
and it is obviously a field which needs to be recycled.
I meant to say CoyoteRequest. :-)
"Fixing" this will create a major security is
Remy Maucherat wrote:
Amy Roh wrote:
The admin logs you out and asks you to reauthenticate yourself again
after
you do "commit". It seems like after the admin gets redeployed, the same
CoyoteRequestFacade loses its userPrincipal in the recycle() method.
What
is the motivation for setting userP
Amy Roh wrote:
The admin logs you out and asks you to reauthenticate yourself again after
you do "commit". It seems like after the admin gets redeployed, the same
CoyoteRequestFacade loses its userPrincipal in the recycle() method. What
is the motivation for setting userPrincipal to null in recyc
The admin logs you out and asks you to reauthenticate yourself again after
you do "commit". It seems like after the admin gets redeployed, the same
CoyoteRequestFacade loses its userPrincipal in the recycle() method. What
is the motivation for setting userPrincipal to null in recycle()? I don't
