Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| docs:2500_config_apps:2000_add_edit_services [2026/07/07 07:09] – aware_admin | docs:2500_config_apps:2000_add_edit_services [2026/07/07 07:32] (current) – aware_admin | ||
|---|---|---|---|
| Line 26: | Line 26: | ||
| ===== Service Will be Protected by OAuth2.0 Protocol ===== | ===== Service Will be Protected by OAuth2.0 Protocol ===== | ||
| - | Tick this checkbox if you want to protect a service. If at least one service should be protected, you will need to deploy a special web application. This web application will manage scopes, clients, will issue access tokens and refresh tokens. | + | Tick this checkbox if you want to protect a service. If at least one service should be protected, you will need to deploy a special web application. This web application will manage scopes, clients, will issue access tokens and refresh tokens. |
| - | - Go to the Edit menu of the Configuration Tool | + | |
| - | - Select the entry with the name " | + | |
| - | Note that thew deployment of the dynamic feature should only be done once | + | |
| - | + | ||
| - | Your service documentation needs to convey to the callers of the service that before calling the service, they need to do the following: | + | |
| - | - Obtain an access token by cand | + | |
| - | - include the access token in the Authorization Bearer HTTP header, for example (< | + | |
| - | - The name of the business space must be in the HTTP header called AW-DOMAIN, for example < | + | |
| - | - The name of the service to call must be in the header called AW-SERVICE for a REST-ful service (for example, < | + | |
| ===== Service Reply ===== | ===== Service Reply ===== | ||
| Line 59: | Line 50: | ||
| - for SOAP Service call: < | - for SOAP Service call: < | ||
| - | <callout type=" | + | <callout type=" |
| ==== Reply Format ==== | ==== Reply Format ==== | ||