OpenIAM connector request template

The below template will help users to gather the required technical information for building a connector that integrates their application’s REST API with OpenIAM. The template below provides two options for integration. Please complete the section applicable to your target system.

⚠️ All fields marked as Required must be completed. Incomplete submissions may delay development or require additional follow-up.

REST API Integration

  1. General information
FieldDescriptionYour response
Company NameYour organization name
Application NameThe target application to integrate with OpenIAM
Primary Technical ContactName, email, and role
Environment(s)Specify usage: Dev / Test / Prod
  1. API details (Required)
FieldDescriptionYour response
Base API URLe.g., https://api.vendor.com/v1/
API DocumentationLink or attachment (Postman, Swagger, PDF, etc.)
Authentication TypeOAuth2, API Key, Basic Auth, JWT, etc.
Service account credentialsCredential to use if Basic Auth is used.
Token AcquisitionIncludes details or sample requests
Test Environment Access☐ Yes
☐ No
*If yes, provide credentials or access steps
  1. User lookup & search operations (All Required)
OperationEndpoint & MethodNotes
Search Userse.g., GET /users?query=...
List All Userse.g., GET /users
Get User by ID or Usernamee.g., GET /users/{id}
Get User’s Entitlement Membershipse.g., GET `/users/{id}/roles
  1. User lifecycle operations
OperationEndpoint & MethodNotes (required fields, constraints, etc.)
Create User
Update User
Delete User
Disable/Enable User
Reset Password (if applicable)
  1. Entitlement management (All Required)
FieldDescriptionYour response
Does the system support roles, groups, or other entitlements?☐ Yes
☐ No
API to list all available entitlementse.g., /roles, /groups
API to assign entitlement to a usere.g., POST /users/{id}/roles
API to remove entitlement from usere.g., DELETE /users/{id}/roles/{roleId}
API to get current entitlements for a usere.g., GET /users/{id}/roles
  1. Identity attribute mapping & generation rules
Attribute NameRequired?Source ColumnGeneration Rule (if applicable)Collision HandlingNotes
usernameYesfirst_name + last_namefirstName.lastNameAppend number if existsMatches AD identity?
  1. Security constraints
FieldDescriptionYour response
Rate limitsAPI quotas, throttling policies
Firewall / IP AllowlistIf yes, provide steps or list OpenIAM IPs
Required Headers / Custom TokensAny headers, token exchange steps, etc.
  1. Attachments checklist

Please attach or link to the following items:

  • API documentation (Swagger, Postman, PDF, etc.).
  • Sample request/response payloads for each operation.
  • Test credentials or sandbox access instructions (if available).
  1. Confirmation

Please confirm the following before submission:
☐ All required operations and API endpoints have been provided.
☐ API documentation is included.
☐ A test environment is made available to OpenIAM.

Relational database integration

  1. General information
FieldDescriptionYour response
Company NameYour organization name
Application NameThe target application to integrate with OpenIAM
Primary Technical ContactName, email, and role
Environment(s)Specify usage: Dev / Test / Prod
  1. Database connection details
FieldDescriptionYour response
Database Typee.g., Oracle, MSSQL, MySQL, PostgreSQL
JDBC Connection URLe.g., jdbc:mysql://hostname:3306/dbname
Authentication TypeUsername/Password, Windows Auth, etc.
Service Account CredentialsAccount used by OpenIAM to connect
Test Environment Access☐ Yes
☐ No
  1. User lifecycle operations (All Required)
OperationTable/View/SQL or ProcedureNotes (filters, keys, etc.)
Search Users
List All Users
Get User by ID
Create User
Update User
Delete (Soft or Hard)
Disable/Enable User
  1. Entitlement management (All Required)
OperationTable/View/SQL or ProcedureNotes
List Available Roles/Groups
Assign Role/Group to User
Remove Role/Group from User
Get Current User Roles/Groups
  1. Identity attribute mapping & generation rules
Attribute NameRequired?Source ColumnGeneration Rule (if applicable)Collision HandlingNotes
usernameYesfirst_name + last_namefirstName.lastNameAppend number if existsMatches AD identity?
  1. Security constraints
FieldDescriptionYour Response
Firewall / IP AllowlistProvide steps or OpenIAM IPs
Read/Write PermissionsTables/views OpenIAM must access
Database Rate LimitsIf applicable
  1. Attachments checklist

Please attach or link to the following items:

  • ERD (Entity Relationship Diagram) or table descriptions.
  • Sample data or schema exports.
  • SQL examples for each operation (SELECT, INSERT, UPDATE).
  • Test credentials and connection details.
  1. Confirmation

Please confirm the following before submission:
☐ All required operations and procedures have been documented.
☐ Table/view mappings are included.
☐ A test database is accessible to OpenIAM.