omnixys-outbox 3.0.2__tar.gz

omnixys_outbox-3.0.2/.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

omnixys_outbox-3.0.2/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# 📜 Code of Conduct
+
+This project follows the **Omnixys Open Source Contributor Code of Conduct**.  
+All contributors and maintainers are expected to uphold the following standards.
+
+---
+
+## 💬 Our Pledge
+
+We pledge to create an open, welcoming, and respectful community.  
+Everyone—regardless of experience level, nationality, gender identity, or background—is welcome.
+
+---
+
+## 💡 Our Standards
+
+Examples of behavior that contributes to a positive environment include:
+- Using respectful and inclusive language
+- Being considerate of differing viewpoints
+- Accepting constructive feedback gracefully
+- Focusing on collaboration and problem-solving
+
+Unacceptable behaviors include:
+- Harassment, trolling, or derogatory comments
+- Publishing others’ private information
+- Discriminatory or disrespectful conduct
+
+---
+
+## ⚙️ Enforcement
+
+Project maintainers are responsible for clarifying standards and enforcing this Code of Conduct.  
+Violations may result in warnings, temporary bans, or permanent exclusion from the project.
+
+If you witness or experience behavior that violates this Code of Conduct, please contact:
+
+**Omnixys Core Team** – [contact@omnixys.tech](mailto:contact@omnixys.tech)
+
+---
+
+## 📄 Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.
+
+© 2025 Caleb Gyamfi – Omnixys Technologies  
+Licensed under GPL‑3.0‑or‑later

omnixys_outbox-3.0.2/.github/CONTRIBUTING.md

@@ -0,0 +1,116 @@
+# 🤝 Contributing to Omnixys Authentication Service
+
+Thank you for your interest in contributing to the **Omnixys Authentication Service**!  
+This document defines our contribution workflow, coding standards, and pull request guidelines.
+
+---
+
+## 🧩 Development Environment
+
+1. **Fork and clone** the repository  
+   ```bash
+   git clone https://github.com/your-username/omnixys-authentication-service.git
+   cd omnixys-authentication-service
+   ```
+
+2. **Install dependencies**
+   ```bash
+   pnpm install
+   ```
+
+3. **Create a feature branch**
+   ```bash
+   git checkout -b feature/short-description
+   ```
+
+4. **Run and test**
+   ```bash
+   pnpm run lint && pnpm run test
+   ```
+
+---
+
+## ✨ Contribution Types
+
+- 🐛 Bug fixes
+- 💡 New features
+- 🧪 Refactoring and improvements
+- 🧾 Documentation updates
+- 🔒 Security or performance enhancements
+
+---
+
+## 💅 Code Style
+
+- **Language:** TypeScript (NestJS)
+- **Formatter:** Prettier with `.prettierrc.yml`
+- **Linter:** ESLint with strict rules
+- **Imports:** Sorted alphabetically (using Prettier plugin)
+- **Naming:** `camelCase` for variables/functions, `PascalCase` for classes
+- **Comments:** Use English for all code comments and docstrings
+
+Example:
+```ts
+/**
+ * Handles JWT token validation and caching.
+ */
+async validateToken(token: string): Promise<boolean> {
+  // Verify using Keycloak public key
+  return await this.keycloakService.verifyToken(token);
+}
+```
+
+---
+
+## 🧠 Pull Request Guidelines
+
+1. Ensure your branch is up-to-date with `main`:
+   ```bash
+   git pull origin main
+   ```
+
+2. Run code checks before committing:
+   ```bash
+   pnpm run lint && pnpm run test
+   ```
+
+3. Use **conventional commits**:
+   - `feat:` → new feature
+   - `fix:` → bug fix
+   - `docs:` → documentation changes
+   - `refactor:` → code improvement
+   - `test:` → tests only
+
+   Example:
+   ```bash
+   git commit -m "feat: add Redis session TTL refresh logic"
+   ```
+
+4. Submit a **Pull Request (PR)** with a clear title and description:
+   - What problem does this solve?
+   - How was it tested?
+   - Are there related issues?
+
+5. Wait for a **review approval** from the Omnixys Core Team before merging.
+
+---
+
+## 🧾 Code Review Principles
+
+- Keep PRs small, atomic, and easy to review.
+- Write meaningful commit messages.
+- All tests must pass before merge.
+- PRs without tests will not be merged (except documentation).
+
+---
+
+## 🧭 Communication
+
+- Use **English** for all commits, issues, and PR discussions.
+- Prefer GitHub Discussions for architectural or feature debates.
+- Be respectful, constructive, and concise.
+
+---
+
+© 2025 Caleb Gyamfi – Omnixys Technologies  
+Licensed under GPL‑3.0‑or‑later

omnixys_outbox-3.0.2/.github/DISCUSSION_TEMPLATE/authentication_general.yml

@@ -0,0 +1,49 @@
+# @license GPL-3.0-or-later
+# Copyright (C) 2025 Caleb Gyamfi - Omnixys Technologies
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU General Public License for more details.
+#
+# For more information, visit <https://www.gnu.org/licenses/>.
+
+# name: 🧵 General Discussion
+# description: Start an open discussion or share general feedback about the Authentication Service.
+labels: ["general", "authentication"]
+title: "[Authentication Service Discussion] "
+# category: "🧵 General"
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 💬 Topic
+        This space is for open conversations, brainstorming, and general feedback related to the Authentication Service.
+
+  - type: textarea
+    id: topic
+    attributes:
+      label: What would you like to discuss?
+      placeholder: |
+        Examples:
+        - General thoughts on Keycloak integration
+        - Feedback on token handling design
+        - Ideas for improving developer experience
+        - Cross-service communication patterns
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context (optional)
+      placeholder: |
+        Include background information, relevant links, or references to other discussions or issues.
+    validations:
+      required: false

omnixys_outbox-3.0.2/.github/DISCUSSION_TEMPLATE/authentication_idea.yml

@@ -0,0 +1,50 @@
+# @license GPL-3.0-or-later
+# Copyright (C) 2025 Caleb Gyamfi - Omnixys Technologies
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU General Public License for more details.
+#
+# For more information, visit <https://www.gnu.org/licenses/>.
+
+# name: 💡 Authentication Service Idea or Proposal
+# description: Share an idea or suggestion to improve the Authentication microservice.
+labels: ["idea", "authentication"]
+title: "[Authentication Service Idea] "
+# category: "💡 Ideas & Suggestions"
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 💭 Description
+        Propose an improvement, feature, or workflow enhancement for the Authentication Service.
+
+  - type: textarea
+    id: idea
+    attributes:
+      label: What are you proposing?
+      placeholder: |
+        Example ideas:
+        - Add OpenID Connect dynamic client registration
+        - Support passwordless login via WebAuthn
+        - Improve token refresh logging and error handling
+    validations:
+      required: true
+
+  - type: textarea
+    id: benefit
+    attributes:
+      label: Why is this beneficial?
+      placeholder: |
+        Explain the impact:
+        - How does this improve security or developer experience?
+        - Which users or components (Keycloak, Redis, Kafka, JWT) would benefit?
+    validations:
+      required: true

omnixys_outbox-3.0.2/.github/DISCUSSION_TEMPLATE/authentication_implementation.yml

@@ -0,0 +1,73 @@
+# @license GPL-3.0-or-later
+# Copyright (C) 2025 Caleb Gyamfi - Omnixys Technologies
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU General Public License for more details.
+#
+# For more information, visit <https://www.gnu.org/licenses/>.
+
+# name: 🧪 Implementation or Architecture Discussion
+# description: Discuss technical design, architecture, or integration details for the Authentication Service.
+labels: ["🧪 Implementation", "authentication"]
+title: "[Authentication Implementation] "
+# category: "🧪 Implementation Details"
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## ⚙️ Implementation Discussion
+        Use this template to discuss technical topics such as:
+        - Keycloak realm synchronization
+        - Redis session clustering
+        - Kafka event design
+        - GraphQL schema structure or AuthZ strategy
+
+  - type: textarea
+    id: topic
+    attributes:
+      label: Topic
+      placeholder: |
+        Describe the component or concept you'd like to discuss:
+        e.g., "Proposal for token refresh microflow", "Improving user session TTL handling"
+    validations:
+      required: true
+
+  - type: textarea
+    id: details
+    attributes:
+      label: Technical Details
+      placeholder: |
+        Include relevant code snippets, architecture diagrams, or performance observations.
+        Mention technologies (NestJS, Keycloak, Redis, Kafka) involved in this topic.
+    validations:
+      required: true
+
+  - type: textarea
+    id: goal
+    attributes:
+      label: Desired Outcome
+      placeholder: |
+        What is the goal of this discussion?
+        - Clarify design direction
+        - Choose between alternative implementations
+        - Define new integration behavior
+    validations:
+      required: true
+
+  - type: textarea
+    id: references
+    attributes:
+      label: References (optional)
+      placeholder: |
+        Link to related issues, PRs, or documentation.
+        Example: Issue #42 – Keycloak event stream optimization
+    validations:
+      required: false

omnixys_outbox-3.0.2/.github/DISCUSSION_TEMPLATE/authentication_question.yml

@@ -0,0 +1,61 @@
+# @license GPL-3.0-or-later
+# Copyright (C) 2025 Caleb Gyamfi - Omnixys Technologies
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU General Public License for more details.
+#
+# For more information, visit <https://www.gnu.org/licenses/>.
+
+# name: ❓ Authentication Service Question or Support Request
+# description: Ask a question or request help with setup, deployment, or usage of the Authentication Service.
+labels: ["question", "authentication"]
+title: "[Authentication Question] "
+# category: "❓ Questions & Support"
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 🙋 Question
+        Please describe your question or issue as clearly as possible.  
+        ⚠️ **Do not** include any passwords, access tokens, or private keys.
+
+  - type: textarea
+    id: question
+    attributes:
+      label: What do you need help with?
+      placeholder: |
+        Examples:
+        - How do I configure Keycloak for multi-tenant login?
+        - Why does JWT refresh fail when Redis cache is enabled?
+        - How can I debug Kafka event propagation between services?
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      placeholder: |
+        Provide relevant background such as:
+        - Environment (Docker Compose, Local Node, Kubernetes)
+        - Authentication Service version and dependencies
+        - Any related error messages or logs
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant Logs or Output (optional)
+      description: Paste sanitized logs or terminal output that help explain the problem.
+      render: shell
+    validations:
+      required: false

omnixys_outbox-3.0.2/.github/ISSUE_TEMPLATE/authentication_bug_report.yaml

@@ -0,0 +1,87 @@
+# @license GPL-3.0-or-later
+# Copyright (C) 2025 Caleb Gyamfi - Omnixys Technologies
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU General Public License for more details.
+#
+# For more information, visit <https://www.gnu.org/licenses/>.
+
+name: 🐛 Authentication Service Bug Report
+description: Report a reproducible issue or unexpected behavior in the Authentication microservice
+title: '[Authentication Bug] '
+labels: [bug, authentication, needs-triage]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a bug! Please include as much detail as possible.
+
+  - type: input
+    id: summary
+    attributes:
+      label: Bug summary
+      description: What went wrong?
+      placeholder: Login mutation fails with 400 error...
+    validations:
+      required: true
+
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      options:
+        - Low
+        - Medium
+        - High
+        - Critical
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      description: How can we reproduce the bug?
+      placeholder: |
+        1. Start the authentication-service with `pnpm run start:dev`
+        2. Send a login mutation via GraphQL
+        3. Observe error response
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: What did you expect to happen?
+      placeholder: Login mutation should return a valid access token.
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logs or screenshots
+      description: Paste logs or attach screenshots (omit secrets).
+      render: shell
+    validations:
+      required: false
+
+  - type: dropdown
+    id: env
+    attributes:
+      label: Environment
+      options:
+        - Local Development
+        - Docker Compose
+        - Production Deployment
+    validations:
+      required: true

omnixys_outbox-3.0.2/.github/ISSUE_TEMPLATE/authentication_feature_request.yaml

@@ -0,0 +1,48 @@
+# @license GPL-3.0-or-later
+# Copyright (C) 2025 Caleb Gyamfi - Omnixys Technologies
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU General Public License for more details.
+#
+# For more information, visit <https://www.gnu.org/licenses/>.
+
+name: 💡 Authentication Service Feature Request
+description: Suggest a new feature or enhancement for the Authentication microservice
+title: '[Authentication Feature] '
+labels: [enhancement, authentication]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your idea! Please describe clearly what you want to improve.
+
+  - type: input
+    id: title
+    attributes:
+      label: Feature title
+      placeholder: Add MFA support for Keycloak users
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Feature Description
+      placeholder: What should this feature do, and how does it improve authentication flow?
+    validations:
+      required: true
+
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation / Use Case
+      placeholder: Why is this feature important? Describe the real-world problem it solves.
+    validations:
+      required: true

omnixys_outbox-3.0.2/.github/ISSUE_TEMPLATE/authentication_question.yaml

@@ -0,0 +1,73 @@
+# @license GPL-3.0-or-later
+# Copyright (C) 2025 Caleb Gyamfi - Omnixys Technologies
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU General Public License for more details.
+#
+# For more information, visit <https://www.gnu.org/licenses/>.
+
+name: ❓ Authentication Service Question or Help Request
+description: Ask a question or request help regarding setup, configuration, or usage of the Authentication Service.
+title: '[Authentication Question] '
+labels: ['question', 'authentication', 'needs-triage']
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 🙋 Question
+        Please describe your question or issue clearly.  
+        Do **not** include passwords, JWTs, or other sensitive credentials.
+
+  - type: textarea
+    id: question
+    attributes:
+      label: What do you need help with?
+      placeholder: |
+        Example:
+        - How do I configure Keycloak realms for multiple clients?
+        - Why does Redis session caching fail during token refresh?
+        - How can I verify JWT expiration within a NestJS guard?
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Context
+      placeholder: |
+        Describe what you were working on:
+        - Which version of the Authentication Service?
+        - Are you running via Docker Compose, local Node, or Kubernetes?
+        - Any relevant dependencies (Keycloak, Redis, Kafka)?
+    validations:
+      required: true
+
+  - type: dropdown
+    id: environment
+    attributes:
+      label: Environment
+      description: Select the environment where the issue occurs.
+      options:
+        - Local Development
+        - Docker Compose
+        - Kubernetes Cluster
+        - Production Deployment
+    validations:
+      required: false
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant Logs or Error Messages
+      description: Paste sanitized log output or stack traces that help us understand the issue.
+      render: shell
+    validations:
+      required: false

omnixys_outbox-3.0.2/.github/ISSUE_TEMPLATE/authentication_security_vulnerability.yaml

@@ -0,0 +1,61 @@
+# @license GPL-3.0-or-later
+# Copyright (C) 2025 Caleb Gyamfi - Omnixys Technologies
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU General Public License for more details.
+#
+# For more information, visit <https://www.gnu.org/licenses/>.
+
+name: 🔒 Security Vulnerability Report
+description: Report a potential security vulnerability in the Omnixys Authentication Service
+title: '[Authentication Security] '
+labels: [security, urgent, authentication]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ⚠️ **Security Notice**: Please avoid sharing sensitive information publicly.
+        Use this form to responsibly disclose vulnerabilities in the Authentication microservice.
+
+  - type: input
+    id: title
+    attributes:
+      label: Vulnerability summary
+      placeholder: e.g., Token refresh endpoint allows replay attacks
+    validations:
+      required: true
+
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      options:
+        - Low
+        - Medium
+        - High
+        - Critical
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      placeholder: Describe the vulnerability in detail and its potential impact.
+    validations:
+      required: true
+
+  - type: textarea
+    id: mitigation
+    attributes:
+      label: Suggested mitigation
+      placeholder: Provide any ideas on how to fix or mitigate the issue.
+    validations:
+      required: false