WamISSO Documentation

SSO Integration Guide

Connect your application to WamISSO using OAuth 2.0 Authorization Code flow.

Base URL: https://wamisso.rendovations.com
Register as a developer at https://wamisso.rendovations.com/developer/login, get admin approval, then create an OAuth client in the developer portal to obtain a client_id and client_secret. See the developer registration guide for step-by-step instructions.

OAuth 2.0 flow

Endpoints

MethodPathDescription
GET/oauth/authorizeStart login — redirect the user here
POST/oauth/tokenExchange code or refresh token
GET/api/userUser profile (requires Bearer token)
POST/api/sso/logoutRevoke access token (requires Bearer token)
GET/.well-known/openid-configurationOpenID discovery metadata
GET/.well-known/oauth-authorization-serverOAuth metadata

Authorization request

Redirect the browser to:

https://wamisso.rendovations.com/oauth/authorize
  ?client_id={CLIENT_ID}
  &redirect_uri={REDIRECT_URI}
  &response_type=code
  &scope=openid profile email
  &state={RANDOM_STATE}

Token exchange

curl -X POST https://wamisso.rendovations.com/oauth/token \
  -H "Accept: application/json" \
  -d "grant_type=authorization_code" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET" \
  -d "redirect_uri=http://localhost:3000/callback" \
  -d "code=AUTH_CODE_FROM_CALLBACK"

User profile response

{
  "sub": "1",
  "name": "Juan Dela Cruz",
  "email": "user@wamisso.gov.ph",
  "email_verified": true
}

Scopes

ScopeDescription
openidIdentity verification
profileName and basic profile
emailEmail address

Logout (revoke token)

When a user signs out of your application, revoke the OAuth access token so it cannot be reused:

curl -X POST https://wamisso.rendovations.com/api/sso/logout \
  -H "Accept: application/json" \
  -H "Authorization: Bearer ACCESS_TOKEN"
{
  "message": "Successfully logged out",
  "status": "logged_out"
}
Always clear your local session or stored tokens after calling logout, even if the API call fails.

Framework guides

Language guides

Production: Use HTTPS, store secrets securely, and register exact redirect_uri values for each client.