What OAuth does
Without OAuth, every assistant would need a password or a shared key written into its configuration. With OAuth, nobody puts a secret in a config file. The person signs in on the server’s own page, and the assistant gets two tokens in return:- an access token, which it sends with every request and which expires after 15 minutes;
- a refresh token, which it uses to get a new access token without asking the person again.
How it works
Here is what happens the first time Ana adds the server to her assistant and asks it a question. Mapepire is the IBM i database server that the MCP server sends SQL to. The key step is the sign-on in the middle. The MCP server signs on to the IBM i asANA and keeps that connection, so every tool call Ana makes runs its SQL as her. IBM i authority checks, job logs and auditing all name ANA.
When the access token expires, the assistant uses the refresh token to get a new one in the background. Ana only sees the sign-in page again when the sign-in ends.
Choose how people sign in
With your identity provider, Ana signs in at the provider instead of the MCP server, and the server never signs on to the IBM i as her.
Choose IBM i sign-on unless the people using the server don’t have IBM i profiles.
Next steps
Set up IBM i sign-on
Try it on your machine, then open it to your team.
Use your identity provider
Accept tokens from your existing OAuth or OpenID Connect provider.
Security
How people are authenticated, and how to lock the setup down.
Reference
Every setting, default and limit.