absuite-identity

Manage user identity, OAuth flows, and OpenID Connect configurations via the Alliance Business Suite REST API.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/FenixAlliance/ABS.Agents --skill absuite-identity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: absuite-identity
Source: https://github.com/FenixAlliance/ABS.Agents/tree/main/paperclip/skills/absuite-identity
Command: npx skills add https://github.com/FenixAlliance/ABS.Agents --skill absuite-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of managing user identity, OAuth flows, and OpenID Connect configurations for the Alliance Business Suite, removing the need to memorize complex REST endpoint specifications, authentication requirements, and per-endpoint tenant scoping rules.

Core Features & Use Cases

  • OAuth & OIDC Operations: Handle password sign-in, OAuth token issuance, OIDC discovery document retrieval, and JSON Web Key Set (JWKS) fetching for ABS applications.
  • User Identity & Permission Management: Resolve current user identity (WhoAmI), enumerate user permissions, and inspect application role and grant assignments across ABS tenants.
  • Use Case: A developer building an ABS integration can use this Skill to automatically validate user credentials, retrieve the user's tenant-specific permissions, and fetch OIDC configuration for a custom ABS application without manually constructing REST calls.

Quick Start

Use the absuite-identity skill to retrieve the current user's tenant-specific permissions for your ABS application.

Frequently Asked Questions about absuite-identity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage OAuth flows and user identity for Alliance Business Suite REST APIs?

OAuth token issuance and user identity management for ABS are handled via REST API endpoints covering password sign-in and OpenID Connect. A valid bearer token is required to access these protected endpoints.

How do I retrieve the OIDC discovery document and JWKS for my ABS application?

OIDC discovery documents and JSON Web Key Sets (JWKS) are fetched via dedicated ABS REST API endpoints. This retrieves OpenID Connect configurations for custom ABS applications without manual HTTP request construction.

Can I enumerate user permissions and inspect application roles across different ABS tenants?

User permissions and application roles are enumerated across ABS tenants via the WhoAmI endpoint and permission APIs. The system adheres to per-endpoint tenant scoping rules to return role and grant assignments accurately.

Do I need a bearer token to access protected identity endpoints in ABS?

Yes, a valid bearer token is required for accessing protected ABS identity endpoints. This token authenticates requests for user identity resolution and secure OAuth operations.

What are the limitations when updating identity resources via the ABS REST API?

The ABS REST API does not support PATCH operations for identity resources. All OAuth and user identity updates must respect per-endpoint tenant scoping rules during REST API interactions.