Difference between revisions of "I2Rest Advanced Setup"
m |
|||
| Line 2: | Line 2: | ||
* [[Using secured connections]] | * [[Using secured connections]] | ||
| − | * [[i2Rest Gate URL definition using Unix socket]] | + | * [[i2Rest Gate URL definition using Unix socket|Serving incoming connections using Unix sockets]] |
* [[I2Rest_with_syslog|Using syslog with i2Rest Server]] | * [[I2Rest_with_syslog|Using syslog with i2Rest Server]] | ||
* [[Configuring OAuth2 authorization]] | * [[Configuring OAuth2 authorization]] | ||
Revision as of 09:37, 8 July 2020
This section describes configuration options of i2Rest Server. Basic configuration allows only demo server functionality, and must be extended to supply full functional server instancence. Combining examples bellow you can achieve server functionality that suits your requirements.
- Using secured connections
- Serving incoming connections using Unix sockets
- Using syslog with i2Rest Server
- Configuring OAuth2 authorization
- How to allow calls to run_command API
- How to allow calls to management API
- How to call API located on remote IBM i server
- Custom scopes Это на будущее, сейчас можно не описывать. Мы с тобой как-то обсуждали про то, что можно добавить собственный скоуп, использовать его в настройке полномочий и передавать его в сессию
- API configuration examples
i2Rest server should be restarted to aplly your new configuration *.json.
