University of Campinas · Authentication Profile

Unicamp Edat Oidc Authentication

Authentication

University of Campinas secures its APIs with openIdConnect and oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions.

EducationHigher EducationUniversityPublic Research UniversityBrazilLatin AmericaResearch DataOpen DataResearch RepositoryIdentity FederationOAI-PMHDataverseCourse Catalog

Methods: openIdConnect, oauth2 Schemes: 1 OAuth flows: API key in:

Security Schemes

edatOidc openIdConnect

Source

Authentication Profile

generated: '2026-09-01'
method: probed
source: https://seguranca.dados.unicamp.br/realms/edat/.well-known/openid-configuration
note: >-
  Read directly from Unicamp's own OpenID Connect discovery document (HTTP 200, 6,717 bytes,
  probed 2026-09-01). The authorization server is a Keycloak deployment operated by Unicamp on
  its own registrable domain and is the credential authority for the EDAT data platform
  (catalogo.dados.unicamp.br, apoio.dados.unicamp.br, api.dados.unicamp.br). It is separate from
  Unicamp's SAML/Shibboleth identity provider registered in the CAFe federation.
x-operator: institution
summary:
  types:
  - openIdConnect
  - oauth2
issuer: https://seguranca.dados.unicamp.br/realms/edat
discovery: https://seguranca.dados.unicamp.br/realms/edat/.well-known/openid-configuration
endpoints:
  authorization: https://seguranca.dados.unicamp.br/realms/edat/protocol/openid-connect/auth
  token: https://seguranca.dados.unicamp.br/realms/edat/protocol/openid-connect/token
  userinfo: https://seguranca.dados.unicamp.br/realms/edat/protocol/openid-connect/userinfo
  jwks: https://seguranca.dados.unicamp.br/realms/edat/protocol/openid-connect/certs
  introspection: https://seguranca.dados.unicamp.br/realms/edat/protocol/openid-connect/token/introspect
  revocation: https://seguranca.dados.unicamp.br/realms/edat/protocol/openid-connect/revoke
  end_session: https://seguranca.dados.unicamp.br/realms/edat/protocol/openid-connect/logout
  device_authorization: https://seguranca.dados.unicamp.br/realms/edat/protocol/openid-connect/auth/device
  dynamic_client_registration: https://seguranca.dados.unicamp.br/realms/edat/clients-registrations/openid-connect
schemes:
- name: edatOidc
  type: openIdConnect
  description: >-
    OIDC authorization-code flow with PKCE (S256 offered). Declared as DEFAULT_AUTH_URL in the
    catalogo.dados.unicamp.br runtime config and enforced on api.dados.unicamp.br - an
    unauthenticated GET of /suporte/public/sistemas returns 401 {"message":"Unauthorized"}.
  sources:
  - https://seguranca.dados.unicamp.br/realms/edat/.well-known/openid-configuration
  - https://catalogo.dados.unicamp.br/env.js
grant_types:
- authorization_code
- client_credentials
- implicit
- password
- refresh_token
- urn:ietf:params:oauth:grant-type:device_code
- urn:ietf:params:oauth:grant-type:token-exchange
- urn:ietf:params:oauth:grant-type:uma-ticket
- urn:openid:params:grant-type:ciba
token_endpoint_auth_methods:
- private_key_jwt
- client_secret_basic
- client_secret_post
- tls_client_auth
- client_secret_jwt
pkce_methods:
- S256
- plain
id_token_signing_algs:
- RS256
- ES256
- PS256
- EdDSA
- HS256

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/unicamp-edat-oidc-authentication"

All security posture

curl "https://apis.io/api/v1/security?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.