Excerpt |
---|
If your web application is using Geodi Feed API - Feed Method (APP → GEODI ) or Geodi Feed API - Integration with Application Services ( GEODI → APP) then you can perform this service to share authority / role information. |
...
Definition | It is an optional service, not mandatory. If permission definitions provided for FeedApi are LDAP group/user Sid values, it is not required to implement them. Requests are only made for the addresses defined under GEODI / Settings / RoleProvider. Only a system administrator who can access this address can add this definition. You can find sample contents in this folder. If you are using a custom authorization for FeedApi, ask the system administrator who provided you with the GEODI Token the address of your Role / Authorization service and identify it here. I a .net soap api that takes same paramters and returns same object as an output is implemented then | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | [ServiceURL]?m=GetRoles&user={username} {user} or {username} parameters can be used in ServiceURL. Even if the {user}, {username} parameters are not used, the request-user and request-username information is passed in the HTTP Header content.
| |||||||||||||||||||||
HttpMethod | GET | |||||||||||||||||||||
Expected Errors | 401 Unauthorized access / Access denied 403 Forbidden 511 Network Authentication Required | |||||||||||||||||||||
Example GEODI settings file |
| |||||||||||||||||||||
Expected Result |
veya or rules can also be transmitted for GEODI 6.1.0.21248 ve üzeri için kuralda iletilebiliror above.
| |||||||||||||||||||||
Examples |
rule example for GEODI 6.1.0.21248 ve üzeri için kural Örneğiand above
| |||||||||||||||||||||
Example Application |
...