update

Author: quotentiroler

.github/workflows/clean-workflows.yml

@@ -78,7 +78,7 @@ jobs:
             // 3) Delete all successful "Cleanup Workflow Runs" runs (this workflow itself)
             console.log('Looking for successful cleanup workflow runs to delete…');
             for (const run of completed.data.workflow_runs) {
-              if (run.name === 'Cleanup Workflow Runs' && run.conclusion === 'success') {
+              if (run.name.includes('Cleanup') && run.conclusion === 'success') {
                 console.log(`Deleting successful cleanup workflow run ${run.id}`);
                 await github.rest.actions.deleteWorkflowRun({
                   owner,

.github/workflows/comment-commit.yml

@@ -83,7 +83,7 @@ jobs:
               model: process.env.OPENAI_MODEL,
               messages: [
                 { role: "system", content: "You are a concise code diff explainer." },
-                { role: "user", content: `Review this git diff and give me a short summary:\n\n${diff}` }
+                { role: "user", content: `Review this git diff and give me a short but technically accurate summary:\n\n${diff}` }
               ]
             });
             const comment = res.choices.map(c => c.message.content).join("\n\n---\n\n");

.github/workflows/generate-changelog.yml

@@ -128,11 +128,27 @@ jobs:
             if [ -n "$OPENAI_API_KEY" ]; then
               echo "🤖 Creating high-level summary from AI comments..." >&2
               
+              # Set system prompt based on release type
+              case "${{ inputs.release_type }}" in
+                "alpha")
+                  system_prompt="You are a technical documentation specialist creating changelog entries for a development alpha release of a SMART on FHIR Proxy application. Your audience is developers and technical team members who need detailed technical information.\n\nGuidelines for ALPHA releases:\n- Focus on technical implementation details and code changes\n- Include specific component/file changes and technical improvements\n- Use technical terminology and be specific about APIs, endpoints, and architecture\n- Group by: 🔧 Code Changes, 🚀 New Features, ⚡ Performance, 🐛 Bug Fixes, 📚 Documentation\n- Mention specific technical debt addressed or refactoring done\n- Include details about new dependencies, API changes, or breaking changes\n- Keep developer workflow and testing implications in mind"
+                  ;;
+                "beta")
+                  system_prompt="You are a product documentation specialist creating changelog entries for a beta testing release of a SMART on FHIR Proxy application. Your audience includes beta testers, QA engineers, and technical product managers who need functional information.\n\nGuidelines for BETA releases:\n- Focus on user-facing features and functionality changes\n- Explain what users can now do differently or better\n- Balance technical accuracy with user-friendly language\n- Group by: 🚀 New Features, ⚡ Improvements, 🐛 Bug Fixes, � Security, ⚠️ Known Issues\n- Highlight testing scenarios and user experience changes\n- Include any configuration or setup changes needed\n- Mention compatibility and integration improvements\n- Call out any features that need specific testing attention"
+                  ;;
+                "production")
+                  system_prompt="You are an expert technical writer creating changelog entries for a production release of a SMART on FHIR Proxy application. Your audience includes business stakeholders, healthcare administrators, and end users who need meaningful business value information.\n\nGuidelines for PRODUCTION releases:\n- Focus on business value, user benefits, and real-world impact\n- Write in business-friendly language while maintaining technical accuracy\n- Emphasize healthcare workflow improvements and compliance benefits\n- Group by: 🚀 New Features, ⚡ Improvements, 🐛 Bug Fixes, 🔒 Security, 📋 Compliance\n- Highlight operational benefits, cost savings, or efficiency gains\n- Explain how changes improve patient care or administrative workflows\n- Use clear action verbs and quantify improvements where possible\n- Include any training or change management considerations\n- Highlight any breaking changes or important notices prominently"
+                  ;;
+                *)
+                  system_prompt="You are an expert technical writer creating changelog entries for a SMART on FHIR Proxy application. Focus on clear, professional communication of changes and their impact."
+                  ;;
+              esac
+              
               # Create JSON payload with proper escaping
               request_data=$(jq -n \
                 --arg model "gpt-4o-mini" \
-                --arg system_content "You are an expert technical writer creating changelog entries for a SMART on FHIR Proxy application. Your audience includes both technical developers and business stakeholders. Create a professional, well-organized changelog that clearly communicates value and impact.\n\nGuidelines:\n- Group changes by category: 🚀 New Features, ⚡ Improvements, 🐛 Bug Fixes, 🔧 Technical Updates, 🔒 Security\n- Write in business-friendly language while maintaining technical accuracy\n- Focus on user benefits and business value\n- Use active voice and clear action verbs\n- Keep each item concise but informative (1-2 lines max)\n- Avoid technical jargon when possible, explain complex concepts simply\n- Highlight any breaking changes or important notices" \
-                --arg user_content "Create a professional changelog from these commit summaries for a SMART on FHIR Proxy application. Focus on the business value and user impact of each change:\n\n$all_comments" \
+                --arg system_content "$system_prompt" \
+                --arg user_content "Create a professional changelog from these commit summaries for a SMART on FHIR Proxy application (${{ inputs.release_type }} release). Focus on the appropriate level of detail for this release type:\n\n$all_comments" \
                 '{
                   "model": $model,
                   "messages": [

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Maximilian Nussbaumer
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,4 +1,4 @@
-# SMART on FHIR Platform
+# SMART on FHIR Proxy
 
 A comprehensive healthcare application platform implementing the complete SMART App Launch Framework 2.2.0 specification with advanced administrative capabilities, AI-powered assistance, and enterprise-grade security.
 
@@ -10,7 +10,7 @@ A comprehensive healthcare application platform implementing the complete SMART
 
 ## 🏥 Overview
 
-The SMART on FHIR Platform is a complete enterprise solution for managing healthcare applications, users, and FHIR servers in compliance with the SMART App Launch framework. It provides secure OAuth 2.0 flows, comprehensive user management, real-time monitoring, and an AI-powered administrative assistant.
+The SMART on FHIR Proxy is an Open Source solution for managing healthcare applications, users, and FHIR servers in compliance with the SMART App Launch framework. It provides secure OAuth 2.0 flows, comprehensive user management, real-time monitoring, and an AI-powered administrative assistant.
 
 ### Key Features
 
@@ -256,7 +256,7 @@ Each branch automatically triggers appropriate CI/CD workflows with version mana
 
 | Version          | Milestone              | Target Features                           |
 | ---------------- | ---------------------- | ----------------------------------------- |
-| **<0.1.0** | Early Development       | Test deployment, incomplete documentation |
+| **<0.1.0** | Early Development      | Test deployment, incomplete documentation |
 | **v0.1.0** | SMART 2.2.0 Compliance | Complete specification implementation     |
 | **v0.9.0** | AI Enhancement         | Advanced monitoring, predictive analytics |
 | **v1.0.0** | Production Ready       | Enterprise deployment, full documentation |

backend/src/config.ts

@@ -21,10 +21,22 @@ export const config = {
   version: packageJson.version,
 
   keycloak: {
-    baseUrl: process.env.KEYCLOAK_BASE_URL || null,
-    realm: process.env.KEYCLOAK_REALM || null,
-    // Note: clientId and clientSecret no longer needed for admin API
-    // We use the user's token directly
+    // Dynamic getters that read from process.env for real-time updates
+    get baseUrl() {
+      return process.env.KEYCLOAK_BASE_URL || null
+    },
+    
+    get realm() {
+      return process.env.KEYCLOAK_REALM || null
+    },
+    
+    get adminClientId() {
+      return process.env.KEYCLOAK_ADMIN_CLIENT_ID || null
+    },
+    
+    get adminClientSecret() {
+      return process.env.KEYCLOAK_ADMIN_CLIENT_SECRET || null
+    },
 
     // Check if Keycloak is configured
     get isConfigured() {

backend/src/init.ts

@@ -15,14 +15,14 @@ export function isKeycloakAccessible(): boolean {
 /**
  * Check Keycloak connection health with retry logic
  */
-export async function checkKeycloakConnection(): Promise<void> {
+export async function checkKeycloakConnection(retries?: number, interval?: number): Promise<void> {
   // Check if Keycloak is configured
   if (!config.keycloak.isConfigured || !config.keycloak.jwksUri) {
     throw new Error('Keycloak connection verification failed: Not configured')
   }
 
-  const maxRetries = 3;
-  const retryInterval = 10000; // 10 seconds
+  const maxRetries = retries ?? 3; // Default to 3 retries if not specified
+  const retryInterval = interval ?? 5000; // Default to 5 seconds if not specified
 
   for (let attempt = 1; attempt <= maxRetries; attempt++) {
     try {

backend/src/routes/admin/index.ts

@@ -6,6 +6,7 @@ import { launchContextRoutes } from './launch-contexts'
 import { identityProvidersRoutes } from './identity-providers'
 import { smartConfigAdminRoutes } from './smart-config'
 import { clientRegistrationSettingsRoutes } from './client-registration-settings'
+import { keycloakConfigRoutes } from './keycloak-config'
 
 /**
  * Admin routes aggregator - combines all admin functionality
@@ -23,3 +24,4 @@ export const adminRoutes = new Elysia({ prefix: '/admin' })
   .use(identityProvidersRoutes)
   .use(smartConfigAdminRoutes)
   .use(clientRegistrationSettingsRoutes)
+  .use(keycloakConfigRoutes)