Page History
...
An authorization policy is a connector that gets the parameters from the request and maps to a specified service for authorization. In other words, it executes an already defined service for authorization (authorization service) and use some of the request parameters for input.
An Interface references to a defined authorization policy to restrict the access of the interface.
A service references to a defined authorization policy to restrict the usage of the service.
Authorization Policy Identifier
...
Parameter mapping keeps the information of which request parameter is used for input of authorization service.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
...
This policy use an executable service for authorization. The output of the executable is checked with one of the verification methods:
Text Verification
The output is verified with constant predefined string. Authorication succeed if the output is same as predefined string.
If the executable prints "OK" for correct parameters, you can use "OK" with text verification.
Parameter Verification
The output is verified with one of the request parameters. Authorication succeed if the output is same as the value of the specified parameter.
'Not Equals' Verification
The output of the executable service is checked if it is not equals a predefined text value.
If the executable prints "NOK" for incorrect parameters and print a generated ID for correct parameters (unpredictable value), you can use "NOK" with 'Not Equals' verification.
Numeric Expression Verification
The check output of the executable service is checked with a numeric expression. Numeric expression may be smaller than or greater than.
If the executable prints a code number between 200 - 300 for incorrect parameters and print a code number greater than 300 for correct parameters (unpredictable value), you can use "300" with greater than numeric expression verification.