CounterTack · OAuth Scopes

CounterTack OAuth Scopes

OAuth 2.0 probed

CounterTack publishes 13 OAuth 2.0 scopes via the authorizationCode, clientCredentials, deviceCode, implicit, and password flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the CounterTack API on a user’s behalf.

Tokens are issued from https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanySecurityCybersecurityEndpoint SecurityEndpoint Detection and ResponseManaged Detection and ResponseThreat DetectionIncident ResponseSIEM

Scopes: 13 Flows: authorizationCode, clientCredentials, deviceCode, implicit, password Method: probed

OAuth endpoints

Authorization URL
https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/auth

Token URL
https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/token

Flows
authorizationCodeclientCredentialsdeviceCodeimplicitpassword

Scopes (13)

Scope	Description	Flows
titan	Realm-specific scope for the GoSecure Titan platform. Its granted permissions are not publicly documented.
service_account	Realm-specific scope, presumed to accompany client-credentials service accounts. Its granted permissions are not publicly documented.
openid	OpenID Connect core scope; requests an ID token.
profile	OpenID Connect standard scope for basic profile claims.
email	OpenID Connect standard scope for the email and email_verified claims.
address	OpenID Connect standard scope for the address claim.
phone	OpenID Connect standard scope for phone_number claims.
offline_access	OpenID Connect standard scope requesting a refresh token usable while the user is offline.
acr	Keycloak built-in client scope carrying the authentication context class reference.
roles	Keycloak built-in client scope adding realm and client role mappings to the token.
web-origins	Keycloak built-in client scope adding allowed CORS origins to the token.
basic	Keycloak built-in client scope adding the core sub/auth_time claims.
microprofile-jwt	Keycloak built-in client scope emitting MicroProfile JWT claims (upn, groups).

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-11'
method: probed
source: https://login.gosecure.net/realms/gosec-titan/.well-known/openid-configuration
docs: null
note: 'Scopes read verbatim from the scopes_supported array of the GoSecure Titan
  Keycloak realm discovery document. GoSecure publishes no scope/permission reference
  page that could be found, so the descriptions below only distinguish the standard
  OpenID Connect / Keycloak built-in scopes from the two realm-specific scopes
  (titan, service_account); the actual permissions those two grant are not publicly
  documented and have NOT been guessed.'
schemes:
- name: gosec-titan
  source: well-known/countertack-gosec-titan-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/auth
    tokenUrl: https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/token
  - flow: clientCredentials
    tokenUrl: https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/token
  - flow: deviceCode
    deviceAuthorizationUrl: https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/auth/device
  - flow: implicit
    authorizationUrl: https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/auth
  - flow: password
    tokenUrl: https://login.gosecure.net/realms/gosec-titan/protocol/openid-connect/token
scopes:
- scope: titan
  description: Realm-specific scope for the GoSecure Titan platform. Its granted
    permissions are not publicly documented.
  standard: false
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: service_account
  description: Realm-specific scope, presumed to accompany client-credentials service
    accounts. Its granted permissions are not publicly documented.
  standard: false
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: openid
  description: OpenID Connect core scope; requests an ID token.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: profile
  description: OpenID Connect standard scope for basic profile claims.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: email
  description: OpenID Connect standard scope for the email and email_verified claims.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: address
  description: OpenID Connect standard scope for the address claim.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: phone
  description: OpenID Connect standard scope for phone_number claims.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: offline_access
  description: OpenID Connect standard scope requesting a refresh token usable while
    the user is offline.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: acr
  description: Keycloak built-in client scope carrying the authentication context
    class reference.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: roles
  description: Keycloak built-in client scope adding realm and client role mappings
    to the token.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: web-origins
  description: Keycloak built-in client scope adding allowed CORS origins to the token.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: basic
  description: Keycloak built-in client scope adding the core sub/auth_time claims.
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
- scope: microprofile-jwt
  description: Keycloak built-in client scope emitting MicroProfile JWT claims (upn,
    groups).
  standard: true
  sources:
  - well-known/countertack-gosec-titan-openid-configuration.json
summary:
  scope_count: 13
  realm_specific: 2
  standard: 11
x-evidence:
  fetched: '2026-08-11'
  url: https://login.gosecure.net/realms/gosec-titan/.well-known/openid-configuration
  http_status: 200

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/countertack-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.