FIS Authentication
Some requests must be authenticated with an access token from FIS. To obtain one, you must have valid credentials for the institution handling the authentication.
Once obtained, the access token is attached as a Bearer token to every gRPC request via an interceptor in the M10 SDK. No further changes are needed to individual API calls.
Obtaining an Access Token
The CLI uses a device code flow: it requests a verification code, prompts the user to log in via a browser, then waits for the login to complete before storing the token locally at ~/.config/m10/access.token.
Response
Log in at https://login-uat.fisglobal.com/idp/examplebank/verifyUserCode.html?scope=openid
Your verification code is Ij996zHY
Upon successful login the CLI stores the token. All subsequent CLI commands will include it automatically.
Pass --stdout to print the raw access token to the console instead of saving it to disk.
Configuring the SDK
Config file (Rust)
The Rust SDK reads OAuth credentials from a config.toml file in the working directory and fetches a token automatically when the client is created:
Setting up the client
If you already have an access token (for example, obtained out-of-band or via the CLI), pass it directly when constructing the client:
- Rust
- TypeScript
- Dart
To submit requests over HTTP/1 instead of HTTP/2 with the SDKs, use the http option.