Difference between revisions of "I2RESTUALL"
(Created page with "{{DISPLAYTITLE:i2Rest custom User object implementation}} Out of the box, i2Rest server includes custom implementation of the OAuth2 User object. With this implementation, al...") |
m |
||
| Line 5: | Line 5: | ||
To implement this custom User object (service program I2REST/I2RESTUALL), it is required to change i2Rest config object as follows: | To implement this custom User object (service program I2REST/I2RESTUALL), it is required to change i2Rest config object as follows: | ||
| − | < | + | <tt> |
| − | { | + | "OAuth2" : |
| + | { | ||
... | ... | ||
"users": | "users": | ||
| Line 13: | Line 14: | ||
}, | }, | ||
... | ... | ||
| − | }</ | + | } |
| + | </tt> | ||
''This custom implementation requires registered License Key for use Premium version of the i2Rest Server.'' | ''This custom implementation requires registered License Key for use Premium version of the i2Rest Server.'' | ||
Latest revision as of 13:27, 29 March 2022
Out of the box, i2Rest server includes custom implementation of the OAuth2 User object. With this implementation, all user profiles defined on your IBM i server, becomes Users in OAuth2 flows. In contrast to standard implementation, you don't have to register each user in the i2Rest config file. Additionally, in the "users" section, it is not required to specify clients that are allowed to access users - each client registered in "clients" section are allowed to access any user.
To implement this custom User object (service program I2REST/I2RESTUALL), it is required to change i2Rest config object as follows:
"OAuth2" :
{
...
"users":
{
"implementation": "I2REST/I2RESTUALL", "init_entrypoint": "OAuth2_user_init_unlim"
},
...
}
This custom implementation requires registered License Key for use Premium version of the i2Rest Server.
