Steinbach Credit Union · Authentication Profile

Steinbach Credit Union Authentication

Authentication

Steinbach Credit Union secures its APIs with oauth2 and openIdConnect across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, implicit, clientCredentials, password, deviceCode, ciba, jwtBearer, saml2Bearer, and umaTicket flow(s).

Financial ServicesBankingCanadaCredit UnionCooperativeManitobaInteracData AggregationOpen Banking
Methods: oauth2, openIdConnect Schemes: 2 OAuth flows: authorizationCode, implicit, clientCredentials, password, deviceCode, ciba, jwtBearer, saml2Bearer, umaTicket API key in:

Security Schemes

openIdConnect openIdConnect
oauth2 oauth2
· flows: authorizationCode, clientCredentials, deviceCode, ciba

Source

Authentication Profile

steinbach-credit-union-authentication.yml Raw ↑ 
generated: '2026-07-23'
method: searched
source: https://online.scu.mb.ca/.well-known/openid-configuration
docs: https://online.scu.mb.ca/am/oauth2
scope_note: >-
  This is the CONSUMER / member digital-banking identity provider, not a public
  developer API. SCU exposes no first-party developer OAuth API. The endpoints
  below back the online.scu.mb.ca digital banking web/mobile clients (e.g.
  client_id=InternetBanking) and are operated on a ForgeRock/Ping Access
  Management OAuth2 authorization server (issuer https://online.scu.mb.ca/am/oauth2).
  The profile is captured because the OIDC discovery document is anonymously
  published and is the only machine-readable auth contract SCU exposes.
summary:
  types: [oauth2, openIdConnect]
  standard: OpenID Connect / OAuth 2.0 (ForgeRock/Ping AM)
  issuer: https://online.scu.mb.ca/am/oauth2
  oauth2_flows: [authorizationCode, implicit, clientCredentials, password, deviceCode, ciba, jwtBearer, saml2Bearer, umaTicket]
  token_endpoint_auth_methods: [client_secret_post, client_secret_basic, private_key_jwt, self_signed_tls_client_auth, tls_client_auth, none]
  mtls_bound_tokens: true
  pushed_authorization_requests: available
  pkce: [S256, plain]
schemes:
- name: openIdConnect
  type: openIdConnect
  openIdConnectUrl: https://online.scu.mb.ca/.well-known/openid-configuration
  sources: [well-known/steinbach-credit-union-openid-configuration.json]
- name: oauth2
  type: oauth2
  sources: [well-known/steinbach-credit-union-openid-configuration.json]
  flows:
  - flow: authorizationCode
    authorizationUrl: https://online.scu.mb.ca/am/oauth2/authorize
    tokenUrl: https://online.scu.mb.ca/am/oauth2/steinbach_token
  - flow: clientCredentials
    tokenUrl: https://online.scu.mb.ca/am/oauth2/steinbach_token
  - flow: deviceCode
    note: urn:ietf:params:oauth:grant-type:device_code
  - flow: ciba
    note: urn:openid:params:grant-type:ciba (backchannel authentication)
endpoints:
  authorization: https://online.scu.mb.ca/am/oauth2/authorize
  token: https://online.scu.mb.ca/am/oauth2/steinbach_token
  userinfo: https://online.scu.mb.ca/am/oauth2/userinfo
  introspection: https://online.scu.mb.ca/am/oauth2/introspect
  revocation: https://online.scu.mb.ca/am/oauth2/token/revoke
  registration: https://online.scu.mb.ca/am/oauth2/register
  pushed_authorization_request: https://online.scu.mb.ca/am/oauth2/par
  end_session: https://online.scu.mb.ca/am/oauth2/connect/endSession
  jwks_uri: https://online.scu.mb.ca/am/oauth2/connect/jwk_uri