Hello all:
I'm writing an authentication handler in the Security inflow phase. (clients don't support ws-security). If authentication is successful, intent was to generate a unique id that is set in the soap reply header via an outflow phase handler. Clients would reuse this unique id as an authentication token on subsequent requests. I tried to create the unique id in the security inflow phase handler and save to the service context via setProperty(), but the service context is null. Even if I delay id creation until the outflow handler, the inflow handler would still have to notify the outflow handler that authentication was successful by passing some sort of value, which I can't save in the service context.
1. Am I correct in assuming the reason why Service context is null is that it is initialized in later in flow phases?
2. Can anyone suggest a solution on how to pass the unique id to an outflow handler?
TIA.
DP
- Axis2 v1.0: Cannot add property to Service Context from S... D P
- Re: Axis2 v1.0: Cannot add property to Service Conte... Ruchith Fernando
