Page History
You can control the access to your interface with authorization policy.
Usage:
Code Block | ||||
---|---|---|---|---|
| ||||
<communication> <httpInterface authorizationName="checkHttpUserPass" hostname="localhost" port="1655"/> </communication> |
...
Code Block | ||||
---|---|---|---|---|
| ||||
<security> <executableAuthorization name="checkHttpUserPass" serviceName="concatArgumentscheckUserPassService" > <parameterMapping > <mapRow authParam="username" serviceParam="userid"/> <mapRow authParam="password" serviceParam="plain_password"/> </parameterMapping> <expectedResult><text>OK</text></expectedResult> </executableAuthorization> </security> |
We should map username and password fields to
The username and password parameters are the
...
parameters to input parameters of the authorization service (checkUserPass)
Interface authorization passes the username and password attributes of the server request (see Server Request Example) to checkUserPassService as userid and plain_password parameters.
Then checks the output of the service with "OK" text in the example.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<request username="mobileuser" password="ileri"> <job ....> .. .. </job> </request> |