Hi,
Did you mean to ask how to control access to the methods after they
are exposed ? If this is part of the business logic then you will have
to do it your way.
You can also try doing this by operation context injection since for
basic authentication the user name and password gets copied to the
message context.
Please see [1] for an explanation of how to do context injection
Ajith
[1] http://www.wso2.net/kb/106
On 7/12/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi ;
Add following entry into services.xml
excludeOperations
operationop1/operation
/excludeOperations
[EMAIL PROTECTED] wrote:
Hi,
Currently, to control user access on exposed methods in my
WebServices, I pass username/password together with the parameters of
the exposed method. Is there a better way to do this? Any advise
would be helpful.
thank you,
Joseph
--
Thanks,
Deepal
~Future is Open~
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ajith Ranabahu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
