OpenID Connect configuration
AnybanQID is a standard OpenID Connect provider. Point any certified client library at the issuer below and it will discover everything on this page automatically — you rarely need to copy an endpoint by hand.
Issuer
https://id.anybanq.lk/oidcYour library discovers everything below from
/oidc/.well-known/openid-configuration
— also served at /.well-known/openid-configuration, which shows this page in a browser
and the raw JSON to every other client.
Discover it in code
// Node — openid-client const issuer = await Issuer.discover('https://id.anybanq.lk/oidc'); const client = new issuer.Client({ client_id, client_secret, redirect_uris }); // Redirect the user; they approve on their phone. const url = client.authorizationUrl({ scope: 'openid profile', acr_values: 'loa2', code_challenge_method: 'S256', });
Endpoints
| Authorizationauthorization_endpoint | https://id.anybanq.lk/oidc/oauth2/authorizeStart an Authorization Code + PKCE login; the user approves on their phone. |
| Tokentoken_endpoint | https://id.anybanq.lk/oidc/oauth2/tokenExchange the code (or poll a CIBA request) for tokens. |
| UserInfouserinfo_endpoint | https://id.anybanq.lk/oidc/oauth2/userinfoFetch claims for the access token's subject. |
| JWKSjwks_uri | https://id.anybanq.lk/oidc/.well-known/jwks.jsonPublic keys for verifying ID token signatures. |
| Introspectionintrospection_endpoint | https://id.anybanq.lk/oidc/oauth2/introspectCheck whether a token is still active. |
| Revocationrevocation_endpoint | https://id.anybanq.lk/oidc/oauth2/revokeRevoke a refresh or access token. |
| End sessionend_session_endpoint | https://id.anybanq.lk/oidc/oauth2/logoutRP-initiated logout. |
| CIBAbackchannel_authentication_endpoint | https://id.anybanq.lk/oidc/oauth2/bc-authorizeDecoupled auth for call centre, POS and kiosk — no browser on the user's side. |
What this provider supports
Grant types
authorization_code refresh_token client_credentials urn:openid:params:grant-type:ciba
grant_types_supported
Scopes
openid profile email phone roles offline_access
scopes_supported
Claims
sub name email phone_number acr amr sid roles
claims_supported
Assurance levels
loa1 loa2 loa3
acr_values_supported
ID token signing
ES256
id_token_signing_alg_values_supported
Client authentication
client_secret_basic client_secret_post none
token_endpoint_auth_methods_supported
PKCE
S256
code_challenge_methods_supported
Response types
code
response_types_supported
Response modes
query
response_modes_supported
Subject types
public
subject_types_supported
CIBA delivery
poll
backchannel_token_delivery_modes_supported
CIBA request signing
ES256
backchannel_authentication_request_signing_alg_values_supported
Get credentials
Client IDs and secrets are issued per application. Register one in the developer portal, or talk to us about an integration.
Open the developer portal →